On Mon, Jun 2, 2014 at 2:01 PM, Michael S. Tsirkin <mst@xxxxxxxxxx> wrote:
>
> [mst@robin linux]$ git request-pull net-next/master git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git net-next
> warn: No match for commit 2ae76693b8bcabf370b981cd00c36cd41d33fabc found at git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
> warn: Are you sure you pushed 'net-next' there?
git request-pull is clearly correct. There is no "net-next" in that
public repository.
It *used* to be that request-pull then magically tried to fix it up
for you, which in turn resulted in the guess not being right, like
pointing to the wrong branch that just happened to have the same SHA1,
or pointing to a branch when it _should_ have pointed to a tag.
Now, if you pushed your local "net-next" branch to another branch name
(I can find a branch name called "vhost-next" at that repository, then
you can *tell* git that, using the same syntax you must have used for
the push.
So something like
git request-pull net-next/master
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
net-next:vhost-next
should work so that git doesn't end up having to guess (and
potentially guessing wrong).
But it may actually be a simpler driver error, and you wanted to use
"vhost-next", and that "net-next" was actually incorrect?
Linus
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html