git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Mike Hommey <mh@glandium.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn fetch updating master
Date: Thu, 16 Aug 2007 01:03:49 -0700	[thread overview]
Message-ID: <20070816080349.GA16849@muzzle> (raw)
In-Reply-To: <20070815181228.GA6363@glandium.org>

Mike Hommey <mh@glandium.org> wrote:
> Hi,
> 
> I was wondering why the master branch was hardcoded to be updated in
> post_fetch_checkout() in git-svn. Why not allow to use another branch ?

It shouldn't update master if it the branch already exists and is a
valid ref.

The default for git-clone is to create "master", too, so I wanted
git-svn clone behavior to be the same.

-- 
Eric Wong

  reply	other threads:[~2007-08-16  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 18:12 git-svn fetch updating master Mike Hommey
2007-08-16  8:03 ` Eric Wong [this message]
2007-08-16  8:27   ` Mike Hommey
2007-08-16  9:03     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070816080349.GA16849@muzzle \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).