From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Daniel Barkalow" <barkalow@iabervon.org>,
git@vger.kernel.org, "Junio C Hamano" <junkio@cox.net>
Subject: Re: builtin-fetch code with messy history
Date: Tue, 19 Jun 2007 13:57:00 +0200 [thread overview]
Message-ID: <81b0412b0706190457l730d9b6ehc87471808e553c37@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706191249480.4059@racer.site>
On 6/19/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > 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.
Right, missed it. Sounds like we have a plan
next prev parent reply other threads:[~2007-06-19 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 7:12 builtin-fetch code with messy history Daniel Barkalow
2007-06-19 9:40 ` Johannes Schindelin
2007-06-19 10:13 ` Alex Riesen
2007-06-19 11:11 ` Johannes Schindelin
2007-06-19 11:47 ` Alex Riesen
2007-06-19 11:51 ` Johannes Schindelin
2007-06-19 11:57 ` Alex Riesen [this message]
2007-06-19 16:46 ` Jakub Narebski
2007-06-19 16:49 ` Daniel Barkalow
2007-06-19 17:38 ` Junio C Hamano
2007-06-19 19:47 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0706190457l730d9b6ehc87471808e553c37@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).