All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Frediano Ziglio <freddy77@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/5] qcow: coroutines cleanup
Date: Fri, 22 Jul 2011 15:39:01 +0200	[thread overview]
Message-ID: <4E297D75.1080309@redhat.com> (raw)
In-Reply-To: <CAHt6W4cf2n82YhXgdsPYUCDWfdNOQEsZsyYh38-K7t9ODtyVyw@mail.gmail.com>

Am 22.07.2011 15:24, schrieb Frediano Ziglio:
> 2011/7/22 Stefan Hajnoczi <stefanha@gmail.com>:
>> On Fri, Jul 22, 2011 at 11:10 AM, Kevin Wolf <kwolf@redhat.com> wrote:
>>> Am 22.07.2011 11:26, schrieb Frediano Ziglio:
>>>> - you can use scripts/checkpatch.pl to check your patches before send
>>
>> I updated the SubmitAPatch wiki earlier this week.
>>
>> Stefan
>>
> 
> Good, now wiki is working (it seems somebody is attacking Qemu
> sites... yesterday the ML).
> 
> http://git.qemu.org/git/qemu.git/ is not working so all links give 404.
> 
> I added some notes, yes checkpatch was already in the page.
> 
> About git commands to send multiple patches, I use
> 
>   git format-patch --cover-letter -s -M origin/original_branch_name
> --subject-prefix='PATCH vXX' -o outgoing/
> 
> edit manually cover letter and
> 
>   git send-email --to='maintainer@domain' --cc='qemu-devel@nongnu.org'
> outgoing/*
> 
> are these command correct or there is a better way?

Looks correct to me. I usually use -s already for commits, so I don't
need it in format-patch, and I don't use -M (maybe I should), but
otherwise it's more or less the same as I use.

Kevin

  reply	other threads:[~2011-07-22 13:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 13:56 [Qemu-devel] [RFC PATCH 0/5] qcow: coroutines cleanup Frediano Ziglio
2011-07-20 13:56 ` [Qemu-devel] [RFC PATCH 1/5] qcow: allocate QCowAIOCB structure using stack Frediano Ziglio
2011-07-20 13:56 ` [Qemu-devel] [RFC PATCH 2/5] qcow: QCowAIOCB field cleanup Frediano Ziglio
2011-07-22  7:01   ` Kevin Wolf
2011-07-20 13:56 ` [Qemu-devel] [RFC PATCH 3/5] qcow: move some blocks of code to avoid useless variable initialization Frediano Ziglio
2011-07-20 13:56 ` [Qemu-devel] [RFC PATCH 4/5] avoid dandling pointers Frediano Ziglio
2011-07-22  7:02   ` Kevin Wolf
2011-07-22  9:29     ` Frediano Ziglio
2011-07-20 13:56 ` [Qemu-devel] [RFC PATCH 5/5] qcow: small optimization initializing QCowAIOCB Frediano Ziglio
2011-07-22  7:04 ` [Qemu-devel] [RFC PATCH 0/5] qcow: coroutines cleanup Kevin Wolf
2011-07-22  9:26   ` Frediano Ziglio
2011-07-22 10:10     ` Kevin Wolf
2011-07-22 11:00       ` Stefan Hajnoczi
2011-07-22 13:24         ` Frediano Ziglio
2011-07-22 13:39           ` Kevin Wolf [this message]
2011-07-22 13:48           ` Gerd Hoffmann
2011-07-22 20:09       ` Frediano Ziglio
2011-07-25  7:53         ` Kevin Wolf

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=4E297D75.1080309@redhat.com \
    --to=kwolf@redhat.com \
    --cc=freddy77@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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.