Re: [1.8.0] Provide proper remote ref namespaces

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

 



On Mon, 7 Feb 2011, Johan Herland wrote:

> In practice, this discussion boils down to whether we should use
> 
>     remote.origin.fetch = refs/tags/*:refs/remotes/origin/tags/*
> or
>     remote.origin.fetch = refs/tags/*:refs/tags/*
> 
> as the default refspec for tags. 

It clearly should be (and should have been from the start) the former 
one.

> AFAICS, we both agree that whichever 
> refspec is chosen by default, it should be possible for the user to (fairly 
> easily) override, and use the other refspec instead.

Indeed.

And as you propose, the _usage_ of tags should largely be unchanged as 
in most cases there won't be any ambiguity, and therefore using "git log 
v1.7.0" will just work even if the v1.7.0 tag is actually 
refs/remotes/origin/tags/v1.7.0.

So I hardly see what it is that people are unhappy about in this 
proposal.


Nicolas
--
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]