From: "Michael S. Tsirkin" <mst@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] request-pull: resurrect for-linus -> tags/for-linus DWIM
Date: Sun, 18 May 2014 11:33:05 +0300 [thread overview]
Message-ID: <20140518083305.GB28462@redhat.com> (raw)
In-Reply-To: <1400263070-15312-1-git-send-email-gitster@pobox.com>
On Fri, May 16, 2014 at 10:57:50AM -0700, Junio C Hamano wrote:
> Older versions of Git before v1.7.10 did not DWIM
>
> $ git pull $URL for-linus
>
> to the tag "tags/for-linus" and the users were required to say
>
> $ git pull $URL tags/for-linus
>
> instead. Because newer versions of Git works either way,
> request-pull used to show tags/for-linus when asked
>
> $ git request-pull origin/master $URL for-linus
>
> The recent updates broke this and in the output we see "for-linus"
> without the "tags/" prefix.
>
> As v1.7.10 is more than 2 years old, this should matter very little
> in practice, but resurrecting it is very simple.
Well RHEL6 apparently comes with git 1.7.1, there are
probably others.
The problem isn't theorectical actually,
the reason I noticed the change in behaviour is because one of
my pull requests got bounced because of it:
http://article.gmane.org/gmane.comp.emulators.qemu/273121
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Tested-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
> * I _think_ the fix, without breaking the spirit of Linus's "I do
> not want the thing DWIM based on what the remote end has"
> original, would be as simple as this patch. We can queue it as a
> regression fix and do another round of -rc4 if those who depend
> on request-pull heavily feel strongly about it.
>
> git-request-pull.sh | 6 ++++++
> t/t5150-request-pull.sh | 8 +++++++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/git-request-pull.sh b/git-request-pull.sh
> index b67513a..d6648b2 100755
> --- a/git-request-pull.sh
> +++ b/git-request-pull.sh
> @@ -118,6 +118,12 @@ then
> status=1
> fi
>
> +# Special case: turn "for_linus" to "tags/for_linus" when it is correct
> +if test "$ref" = "refs/tags/$pretty_remote"
> +then
> + pretty_remote=tags/$pretty_remote
> +fi
> +
> url=$(git ls-remote --get-url "$url")
>
> git show -s --format='The following changes since commit %H:
> diff --git a/t/t5150-request-pull.sh b/t/t5150-request-pull.sh
> index 75d6b38..93e2c65 100755
> --- a/t/t5150-request-pull.sh
> +++ b/t/t5150-request-pull.sh
> @@ -223,7 +223,13 @@ test_expect_success 'pull request format' '
> git request-pull initial "$downstream_url" tags/full:refs/tags/full
> ) >request &&
> sed -nf fuzz.sed <request >request.fuzzy &&
> - test_i18ncmp expect request.fuzzy
> + test_i18ncmp expect request.fuzzy &&
> +
> + (
> + cd local &&
> + git request-pull initial "$downstream_url" full
> + ) >request &&
> + grep ' tags/full$'
> '
>
> test_expect_success 'request-pull ignores OPTIONS_KEEPDASHDASH poison' '
> --
> 2.0.0-rc3-434-g1ba2fe8
next prev parent reply other threads:[~2014-05-18 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 17:57 [PATCH] request-pull: resurrect for-linus -> tags/for-linus DWIM Junio C Hamano
2014-05-18 8:33 ` Michael S. Tsirkin [this message]
2014-05-19 16:30 ` Junio C Hamano
2014-06-02 7:06 ` Johannes Sixt
2014-06-02 18:05 ` 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=20140518083305.GB28462@redhat.com \
--to=mst@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).