From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alex Riesen <raa.lkml@gmail.com>
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 12:11:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706191210020.4059@racer.site> (raw)
In-Reply-To: <81b0412b0706190313g74765babk38309dd838f3f585@mail.gmail.com>
Hi,
On Tue, 19 Jun 2007, Alex Riesen wrote:
> 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
next prev parent reply other threads:[~2007-06-19 11:12 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 [this message]
2007-06-19 11:47 ` Alex Riesen
2007-06-19 11:51 ` Johannes Schindelin
2007-06-19 11:57 ` Alex Riesen
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=Pine.LNX.4.64.0706191210020.4059@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@gmail.com \
/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).