From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] posting patches in pull requests (was Re: [PATCH 08/29] cpu: Add qemu_for_each_cpu())
Date: Thu, 02 May 2013 13:19:11 -0500 [thread overview]
Message-ID: <87li7xp7mo.fsf@codemonkey.ws> (raw)
In-Reply-To: <51829B71.60306@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Il 02/05/2013 18:06, Michael S. Tsirkin ha scritto:
>> On Thu, May 02, 2013 at 10:52:47AM -0500, Anthony Liguori wrote:
>>> Peter Maydell <peter.maydell@linaro.org> writes:
>>>
>>>> On 2 May 2013 16:30, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>>> /me changes his scripts...
>>>>>
>>>>> -s/PATCH/PULL/ if (/PATCH 0+\\//);
>>>>> +s/PATCH/PULL/ if (/^Subject:/);
>>>>>
>>>>> Yes, Perl...
>>>>
>>>> Heh, I use sed for this bit:
>>>> sed -i -e 's/^Subject: \[PULL\(.*\)].*/Subject: [PULL\1]
>>>> '"$BRANCHPFX"' queue/;/^$/q' "$COVERLETTER"
>>>
>>> You can also just do git format-patch --subject-prefix=PULL and avoid
>>> any fixups...
>
> I still want to avoid any mistakes in case I override the subject prefix
> (e.g. to include 1.5)... Keeping the substitution is cheap and a nice
> safety net.
>
>> Don't forget -M please, especially if you are Paolo :)
>
> Or
>
> [diff]
> renames = true
> renamelimit = 2000
BTW, this is all great stuff to put in a SubmitAPullRequest page on the
wiki. I don't send pull requests so I don't have a script to do this,
but I'd encourage those that do to share their scripts on the wiki.
Regards,
Anthony Liguori
>
> Paolo
next prev parent reply other threads:[~2013-05-02 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 13:51 [Qemu-devel] posting patches in pull requests (was Re: [PATCH 08/29] cpu: Add qemu_for_each_cpu()) Michael S. Tsirkin
2013-05-02 14:09 ` Peter Maydell
2013-05-02 14:17 ` Michael S. Tsirkin
2013-05-02 14:21 ` Peter Maydell
2013-05-02 14:22 ` Michael S. Tsirkin
2013-05-02 14:46 ` Gerd Hoffmann
2013-05-02 14:57 ` Peter Maydell
2013-05-02 15:59 ` Andreas Färber
2013-05-02 16:08 ` Peter Maydell
2013-05-02 16:11 ` Michael S. Tsirkin
2013-05-02 17:09 ` Andreas Färber
2013-05-02 18:15 ` Anthony Liguori
2013-05-02 15:01 ` Stefan Hajnoczi
2013-05-02 15:30 ` Paolo Bonzini
2013-05-02 15:33 ` Peter Maydell
2013-05-02 15:52 ` Anthony Liguori
2013-05-02 15:55 ` Peter Maydell
2013-05-02 16:06 ` Michael S. Tsirkin
2013-05-02 16:59 ` Paolo Bonzini
2013-05-02 18:19 ` Anthony Liguori [this message]
2013-05-03 0:15 ` Peter Crosthwaite
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=87li7xp7mo.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).