qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 0/3] MIPS queue


From: Peter Maydell
Subject: Re: [Qemu-devel] [PULL 0/3] MIPS queue
Date: Mon, 30 Oct 2017 14:20:58 +0000

On 30 October 2017 at 14:09, Yongbok Kim <address@hidden> wrote:
> On 23/10/2017 15:46, Yongbok Kim wrote:
>>
>> The following changes since commit
>> e822e81e350825dd94f41ee2538ff1432b812eb9:
>>
>>    Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request'
>> into staging (2017-10-20 15:04:00 +0100)
>>
>> are available in the git repository at:
>>
>>    git://github.com/yongbok/upstream-qemu.git target-mips.next
>>
>> ----------------------------------------------------------------
>> MIPS patches 2017-10-23
>>
>> Changes:
>> Update email addresses of Yongbok Kim, James Hogan and Paul Burton.
>>
>> ----------------------------------------------------------------
>>
>> James Hogan (1):
>>    MAINTAINERS: Update James Hogan's email address
>>
>> Paul Burton (1):
>>    MAINTAINERS: Update Paul Burton's email address
>>
>> Yongbok Kim (1):
>>    MAINTAINERS: Update Yongbok Kim's email address
>>
>>   .mailmap    |    3 +++
>>   MAINTAINERS |   10 +++++-----
>>   2 files changed, 8 insertions(+), 5 deletions(-)
>>
>>
>
> Ping?

I only notice pull requests if they contain the magic words
"for you to fetch changes up to", which yours does not.
'git request-pull' includes this in its output, so you should
probably make sure your workflow is using that.

I tried applying this, but git complains:
error: remotes/yongbok/target-mips.next: cannot verify a non-tag
object of type commit.

Pull requests should quote a gpg-signed tag name, not a branch.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]