Re: builtin-fetch code with messy history

From: Alex Riesen <raa.lkml@gmail.com>
Date: Jun 19, 2007, 11:47 UTC
Message-ID: <81b0412b0706190447y37c3aedbya42b7a3d5703322c@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0706191210020.4059@racer.site>

On 6/19/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 13 quoted lines

> > >
> > > 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?

...by suggesting to use a nice conversion script which we don't have.

BTW, as far as I can see, git-remote reads old configuration just fine, so it probably will a very simple script: read all and write all. Well, the "all" part of it can be a bit complicated, but aside from that...