Re: 2.0.0 regression? request pull does not seem to find head

Linus Torvalds <torvalds <at> linux-foundation.org> writes:

On Mon, Jun 2, 2014 at 2:01 PM, Michael S. Tsirkin <mst <at> redhat.com>

wrote:

quoted

[mst <at> robin linux]$ git request-pull net-next/master

git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git net-next

quoted

warn: No match for commit 2ae76693b8bcabf370b981cd00c36cd41d33fabc found

at git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git

quoted

warn: Are you sure you pushed 'net-next' there?

git request-pull is clearly correct. There is no "net-next" in that
public repository.

I am seeing something similar:

$ git request-pull master origin > /dev/null
warn: No match for commit 64ea29197d5e13772b1f7b6c24feaa79cc97d997 found at
origin
warn: Are you sure you pushed 'HEAD' there?

but I pushed 64ea29197d5e13772b1f7b6c24feaa79cc97d997:

$ git show-ref bug_fix/init_report
64ea29197d5e13772b1f7b6c24feaa79cc97d997 refs/heads/bug_fix/init_report
64ea29197d5e13772b1f7b6c24feaa79cc97d997 
refs/remotes/origin/bug_fix/init_report

The warning goes away if I give an explicit end commit.

Should the default value for $remote in the call to $find_matching_ref be
$head rather than HEAD (and similarly for the warning message)?

   --James