From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.iabervon.org>
Cc: Jacob Keller <jacob.keller@gmail.com>, git@vger.kernel.org
Subject: Re: refspecs with '*' as part of pattern
Date: Tue, 07 Jul 2015 09:28:45 -0700 [thread overview]
Message-ID: <xmqqbnfo3paa.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1507062208580.2241@iabervon.iabervon.org> (Daniel Barkalow's message of "Mon, 6 Jul 2015 22:20:24 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.iabervon.org> writes:
> 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.
next prev parent reply other threads:[~2015-07-07 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 18:31 refspecs with '*' as part of pattern Jacob Keller
2015-07-06 23:01 ` Junio C Hamano
2015-07-06 23:39 ` Jacob Keller
2015-07-07 2:20 ` Daniel Barkalow
2015-07-07 2:33 ` Jacob Keller
2015-07-07 7:22 ` Jacob Keller
2015-07-07 16:28 ` Junio C Hamano [this message]
2015-07-07 23:20 ` Jacob Keller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbnfo3paa.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.iabervon.org \
--cc=git@vger.kernel.org \
--cc=jacob.keller@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).