From: "Michael S. Tsirkin" <mst@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 2.0.0 regression? request pull does not seem to find head
Date: Tue, 3 Jun 2014 00:34:56 +0300 [thread overview]
Message-ID: <20140602213456.GB17832@redhat.com> (raw)
In-Reply-To: <xmqqzjhv2e9u.fsf@gitster.dls.corp.google.com>
On Mon, Jun 02, 2014 at 02:27:25PM -0700, Junio C Hamano wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > Looks like pull requests no longer work for me on linux.
>
> Wasn't "does not seem to find head" was very much deliberate?
I'm sorry I don't understand what you are asking here.
Same thing happens if I use a branch name explicitly, not just HEAD.
> Linus's patch wanted the users to explicitly tell the tool, without
> tool trying to be too helpful and risking to guess incorrectly.
So this is an intentional behaviour change?
Which patch do you refer to?
> > Some other trees (non-linux) work fine but I didn't yet
> > check whether it's the local or the remote tree that's
> > at issue.
> >
> > Or maybe it's a configuration change that I missed?
> >
> > Note: I have
> > [push]
> > default = matching
> > configured in .gitconfig.
>
> This should not affect anything in request-pull, I think.
I just thought I'd mention this.
push behaviour is the only big incompatible change I'm aware
of between 1.8 which works for me and 2.0 which doesn't.
--
MST
next prev parent reply other threads:[~2014-06-02 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 21:01 2.0.0 regression? request pull does not seem to find head Michael S. Tsirkin
2014-06-02 21:27 ` Junio C Hamano
2014-06-02 21:34 ` Michael S. Tsirkin [this message]
2014-06-02 21:36 ` Linus Torvalds
2014-06-02 22:10 ` James Spencer
2014-06-04 18:40 ` Michael S. Tsirkin
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=20140602213456.GB17832@redhat.com \
--to=mst@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.org \
/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).