All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 00/32] Misc (mostly i386) patches for 2021-05-11
Date: Thu, 13 May 2021 20:12:35 +0100	[thread overview]
Message-ID: <CAFEAcA_EkFT2UCgGsgHYrFNZNn0S42aWOzw1DC+9OEzuerFvTw@mail.gmail.com> (raw)
In-Reply-To: <20210512084020.606871-1-pbonzini@redhat.com>

On Wed, 12 May 2021 at 09:43, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> The following changes since commit e58c7a3bba3076890592f02d2b0e596bf191b5c2:
>
>   Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20210510-1' into staging (2021-05-10 17:28:11 +0100)
>
> are available in the Git repository at:
>
>   https://gitlab.com/bonzini/qemu.git tags/for-upstream
>
> for you to fetch changes up to e804f892b90e58861edd79aafa4d1f4dbdeb3819:
>
>   coverity-scan: list components, move model to scripts/coverity-scan (2021-05-12 04:06:50 -0400)
>
> ----------------------------------------------------------------
> * AccelCPUClass and sysemu/user split for i386 (Claudio)
> * i386 page walk unification
> * Fix detection of gdbus-codegen
> * Misc refactoring
>
> ----------------------------------------------------------------
> v1->v2: dropped incorrect snapshot-load patch

Something weird has happened here.

I think I applied v1 of this pullreq (merge commit 31589644ba069ba06c5
now in master), and then when I came along to try to process this
one the tag was an entirely different set of commits.

Can you check whether what is in master is what you intended, and
send a revert/fixup patch if necessary, please?

PS: my scripts detected this issue:

    Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
    Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
ERROR: pull request includes tag with UTF-8 error in person name

which you probably want to fix before you send a future pullreq
with those commits in. (This error is what nudged me into looking
more closely and realizing something weird was going on...)

Side note: it is more robust if you don't reuse pullreq tag names...

thanks
-- PMM


  reply	other threads:[~2021-05-13 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  8:40 [PULL v2 00/32] Misc (mostly i386) patches for 2021-05-11 Paolo Bonzini
2021-05-13 19:12 ` Peter Maydell [this message]
2021-05-13 20:39   ` Paolo Bonzini
2021-05-14  9:07     ` Peter Maydell

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=CAFEAcA_EkFT2UCgGsgHYrFNZNn0S42aWOzw1DC+9OEzuerFvTw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.