From: Junio C Hamano <gitster@pobox•com>
To: "Michael S. Tsirkin" <mst@redhat•com>
Cc: git@vger•kernel.org
Subject: Re: regression: request-pull with signed tag lacks tags/ in master
Date: Thu, 15 May 2014 15:13:57 -0700 [thread overview]
Message-ID: <xmqqtx8qd716.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140515213925.GI1699@redhat.com> (Michael S. Tsirkin's message of "Fri, 16 May 2014 00:39:25 +0300")
"Michael S. Tsirkin" <mst@redhat•com> writes:
>> My reading of the earlier parts of the series is that Linus wanted
>> us never dwim "for-upstream" to "tags/for-upstream" or any other ref
>> that happens to point at the same commit as for-upstream you have.
>> The changes done for that purpose covered various cases a bit too
>> widely, and "request-pull ... tags/for_upstream" were incorrectly
>> stripped to a request to pull "for_upstream", which was fixed by
>> 5aae66bd (request-pull: resurrect "pretty refname" feature,
>> 2014-02-25).
>>
>> But that fix does not resurrect the dwimming forbid by the earlier
>> parts of the series to turn "for_upstream" into "tags/for_upstream".
>>
>> What would you get if you do this?
>>
>> $ git request-pull origin/master \
>> git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git \
>> tags/for_upstream | grep git.kernel.org
>
>
> I get
> git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
Thanks for double-checking. Let's close this as working as
intended, then.
I personally feel that the "intention" tightened the logic a bit too
much [*1*], and with the updates mentioned in [*2*], existing users
may find it still too tight, but that is what we have today.
[References]
*1* http://thread.gmane.org/gmane.comp.version-control.git/240860
*2* http://thread.gmane.org/gmane.comp.version-control.git/240886
next prev parent reply other threads:[~2014-05-15 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 16:39 regression: request-pull with signed tag lacks tags/ in master Michael S. Tsirkin
2014-05-15 18:50 ` Junio C Hamano
2014-05-15 19:13 ` Junio C Hamano
2014-05-15 21:39 ` Michael S. Tsirkin
2014-05-15 22:13 ` Junio C Hamano [this message]
2014-05-16 16:47 ` Re* " Junio C Hamano
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=xmqqtx8qd716.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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