Re: [PATCH v2 3/3] Teach git-fetch to exploit server side automatic tag following

From: Shawn O. Pearce <spearce@spearce.org>
Date: Mar 6, 2008, 04:53 UTC
Message-ID: <20080306045300.GN8410@spearce.org>
In-Reply-To: <alpine.LSU.1.00.0803051220360.18836@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 18 quoted lines

> On Wed, 5 Mar 2008, Shawn O. Pearce wrote:
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> >  
> > > - should followtags not be the default?
> > 
> > No.  Absolutely not.
> > 
> > The client may not want tag objects from this remote.  It might not want 
> > those tags for all sorts of reasons.  Maybe they are doing a one-shot 
> > pull.  Maybe they don't trust this remote.  Maybe they trust this remote 
> > but this remote is famous for 192M tags containing PDFs of photo images 
> > of build logs printed out on paper, then photographed on a wood table 
> > and finally scanned in at 600 dpi.
> 
> Sorry, I meant to say: "should the followtags feature not be on by default 
> in the circumstances where we would follow tags anyway"...
> 
> Maybe you do that, but I did not see it.

Nope. followtags should be on if the client wants tags, and off if the client does not want tags. Its that simple. There's no reason for the client to disable followtags if the server will actually support it, as disabling it when you do have tags to follow will only cost you extra net latency.

-- 
Shawn.