git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC for 1.7: Do not checkout -b master origin/master on clone

From
EWEric Wong <normalperson@yhbt.net>
Date
Aug 12, 2009, 09:56 UTC
Message-ID
<20090812095656.GA7706@dcvr.yhbt.net>
In-Reply-To
<7v8whpda2l.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
Show 7 quoted lines
> Michael J Gruber <git@drmicha.warpmail.net> writes:
> > - Why does git svn set up a local branch with an svn upstream which is
> > determined by latest svn commit at the time of the first git svn fetch?
> 
> I do not have comments on design decisions in git-svn, other than trusting
> that Eric would exercise good design tastes to make things coherent with
> the git native workflow when the consistency makes sense.

Using 'trunk' (if available) as the master on new fetches does probably make more sense based on the complaints I've gotten. At the time, several projects I cared about did almost all their work in branches and trunk would go untouched for months.... These days most projects I care about are already using git :)

-- 
Eric Wong
Previous: Junio C HamanoNext: Matthieu Moy
Message 4 of 5 in “RFC for 1.7: Do not checkout -b master origin/master on clone”
  1. Michael J GruberAug 11, 2009
  2. Santi BéjarAug 11, 2009
  3. Junio C HamanoAug 12, 2009
  4. Eric WongAug 12, 2009
  5. Matthieu MoyAug 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.