Re: builtin-fetch code with messy history
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jun 19, 2007, 11:51 UTC
- Message-ID
- <Pine.LNX.4.64.0706191249480.4059@racer.site>
- In-Reply-To
- <81b0412b0706190447y37c3aedbya42b7a3d5703322c@mail.gmail.com>
Hi,
On Tue, 19 Jun 2007, Alex Riesen wrote:
Show 17 quoted lines
> On 6/19/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: > > > > > > > > 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.
git.git/contrib/remotes2config.sh
IIRC it was explicitely asked to leave branches/* out of that script, but the original version had it, and it should be easy to include it again.
> 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...
Ciao, Dscho