Re: refspecs with '*' as part of pattern

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 7, 2015, 16:28 UTC
Message-ID: <xmqqbnfo3paa.fsf@gitster.dls.corp.google.com>
In-Reply-To: <alpine.LNX.2.00.1507062208580.2241@iabervon.iabervon.org>

Daniel Barkalow <barkalow@iabervon.iabervon.org> writes:

Show 15 quoted lines

> On Mon, 6 Jul 2015, Junio C Hamano wrote:
>
>> I cannot seem to be able to find related discussions around that
>> patch, so this is only my guess, but I suspect that this is to
>> discourage people from doing something like:
>> 
>> 	refs/tags/*:refs/tags/foo-*
>> 
>> which would open can of worms (e.g. imagine you fetch with that
>> pathspec and then push with refs/tags/*:refs/tags/* back there;
>> would you now get foo-v1.0.0 and foo-foo-v1.0.0 for their v1.0.0
>> tag?) we'd prefer not having to worry about.
>
> That wouldn't be it, since refs/tags/*:refs/tags/foo/* would have the same 
> problem, assuming you didn't set up the push refspec carefully.

Thanks, I was wondering where you were ;-) Nice to hear from you from time to time.

> I think it was mostly that it would be too easy to accidentally do 
> something you don't want by having some other character instead of a 
> slash, like refs/heads/*:refs/heads-*.

Hmm, interesting thought.

But refs/heads/*:refs/heade/* would not be saved, so I do not think that is it, either.