Re: Question regarding git fetch

From: Jeff King <peff@peff.net>
Date: Aug 27, 2009, 21:50 UTC
Message-ID: <20090827215007.GA6231@coredump.intra.peff.net>
In-Reply-To: <7v7hwpors9.fsf@alter.siamese.dyndns.org>

On Thu, Aug 27, 2009 at 02:44:54PM -0700, Junio C Hamano wrote:

Show 12 quoted lines

> Jeff King <peff@peff.net> writes:
> 
> >   # we usually fetch the remote's master straight into our production
> >   # branch for deployment
> >   $ git config remote.origin.fetch refs/heads/master:refs/heads/production
> >
> >   # but today let's demo it first
> >   $ git fetch origin master:demo
> 
> I think this is a good example that any change results from this
> discussion should apply _only_ to cases where command line refspecs lack
> colon (i.e. used to mean "do not store this anywhere but in FETCH_HEAD").

I don't think the colon is the issue. Consider the same situation, but I say:

  # but today let's demo it first
  $ git fetch origin master
  $ git checkout -b demo FETCH_HEAD

I'm still screwed. The issue is that you consider your configured refspec destinations to be precious, and not merely a cache for what's happening on the remote side.

-Peff