Re: builtin-fetch code with messy history

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 19, 2007, 11:11 UTC
Message-ID: <Pine.LNX.4.64.0706191210020.4059@racer.site>
In-Reply-To: <81b0412b0706190313g74765babk38309dd838f3f585@mail.gmail.com>

Hi,

On Tue, 19 Jun 2007, Alex Riesen wrote:

Show 10 quoted lines

> On 6/19/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > >  * when a branch config file section refers to a branches/* remote, the
> > >    merge setting is used (if one is given), even though this isn't useful
> > >    either way.
> > 
> > Maybe this is the right time to cut off branches/* and remotes/*?
> 
> Seconded. Don't use the remotes/ since some months now.
> But... isn't a git package with code of something like 1.4.4 is still
> in some major distributions?

Yes, AFAICT it is Ubuntu "the most up-to-date distro there is". At least many questions on the list and in IRC suggest that.

So, how about checking (at least for a year) in builtin-fetch, if "branches/" or "remotes/" exist, and fail, with a nice message how to move to config-based remotes?

Ciao, Dscho