Re: builtin-fetch code with messy history

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, 19 Jun 2007, Alex Riesen wrote:

> On 6/19/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux