From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PULL for-5.0 00/10] tcg patch queue
Date: Tue, 31 Mar 2020 17:02:51 +0200 [thread overview]
Message-ID: <cb05d334-4473-1ce1-79ac-5d3f99a88764@redhat.com> (raw)
In-Reply-To: <87a73wfzxs.fsf@linaro.org>
On 3/31/20 2:53 PM, Alex Bennée wrote:
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On Tue, 31 Mar 2020 at 04:54, Richard Henderson
>> <richard.henderson@linaro.org> wrote:
>>>
>>> My tcg patch queue, plus one mips patch on request of Aleksander.
>>>
>>>
>>> r~
>>>
>>>
>>> The following changes since commit 5acad5bf480321f178866dc28e38eeda5a3f19bb:
>>>
>>> Merge remote-tracking branch 'remotes/jnsnow/tags/ide-pull-request' into staging (2020-03-28 00:27:04 +0000)
>>>
>>> are available in the Git repository at:
>>>
>>> https://github.com/rth7680/qemu.git tags/pull-tcg-20200330
>>>
>>> for you to fetch changes up to b412378785c1bd95e3461c1373dd8938bc54fb4e:
>>>
>>> decodetree: Use Python3 floor division operator (2020-03-30 11:44:04 -0700)
>>>
>>> ----------------------------------------------------------------
>>> Improve PIE and other linkage
>>> Fix for decodetree vs Python3 floor division operator
>>> Fix i386 INDEX_op_dup2_vec expansion
>>> Fix loongson multimedia condition instructions
>>
>> NB: something in your workflow is leaving the '---' and the following
>> v1/v2 changes info in the commit messages in pull requests. We usually
>> prefer to strip those out.
Same happened to me because I was not applying my own patches (since I
have them locally) but they would then miss the Message-ID tag.
>
> FWIW I used to have a script that reminded me if they were in and
> triggered a clean-up re-base. As people on list have mentioned the
> usefulness of maintaining a Message-Id I have now changed my process to
> always build a PR by applying messages from the list which
>
> a) applies a Message-Id
> b) strips version history
I'm doing that with my own patches now.
>
> The one thing I have to watch out for is if I've started applying tags
> to a branch - so now I only do that once I've made the decision to
> either rev a branch or create a PR.
>
>>
>> Applied, thanks.
>>
>> Please update the changelog at https://wiki.qemu.org/ChangeLog/5.0
>> for any user-visible changes.
>>
>> -- PMM
>
>
prev parent reply other threads:[~2020-03-31 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 3:54 [PULL for-5.0 00/10] tcg patch queue Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 01/10] configure: Drop adjustment of textseg Richard Henderson
2020-03-31 3:54 ` [PATCH for-5.0] tcg/i386: Fix INDEX_op_dup2_vec Richard Henderson
2020-03-31 8:14 ` no-reply
2020-03-31 3:54 ` [PULL for-5.0 02/10] tcg: Remove softmmu code_gen_buffer fixed address Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 03/10] configure: Do not force pie=no for non-x86 Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 04/10] configure: Always detect -no-pie toolchain support Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 05/10] configure: Unnest detection of -z, relro and -z, now Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 06/10] configure: Override the os default with --disable-pie Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 07/10] configure: Support -static-pie if requested Richard Henderson
2020-03-31 13:34 ` Laurent Vivier
2020-03-31 13:44 ` Laurent Vivier
2020-03-31 14:29 ` Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 08/10] target/mips: Fix loongson multimedia condition instructions Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 09/10] tcg/i386: Fix INDEX_op_dup2_vec Richard Henderson
2020-03-31 3:54 ` [PULL for-5.0 10/10] decodetree: Use Python3 floor division operator Richard Henderson
2020-03-31 12:20 ` [PULL for-5.0 00/10] tcg patch queue Peter Maydell
2020-03-31 12:53 ` Alex Bennée
2020-03-31 15:02 ` Philippe Mathieu-Daudé [this message]
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=cb05d334-4473-1ce1-79ac-5d3f99a88764@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).