qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Filip Navara <filip.navara@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: Re: [Qemu-devel] Unclear committer situation
Date: Thu, 3 Dec 2009 10:44:31 +0100	[thread overview]
Message-ID: <5b31733c0912030144n6e615cd0ue20ad31652adeda8@mail.gmail.com> (raw)
In-Reply-To: <AA624F38-F185-45CC-96D5-1E28D46BA017@suse.de>

On Wed, Dec 2, 2009 at 7:56 PM, Alexander Graf <agraf@suse.de> wrote:
>
> On 02.12.2009, at 19:53, Artyom Tarasenko wrote:
>
>> 2009/12/2 Anthony Liguori <anthony@codemonkey.ws>:
>>> Artyom Tarasenko wrote:
>>>>
>>>> 2009/12/1 Alexander Graf <agraf@suse.de>:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> Could someone with commit rights please stand up to feel responsible for
>>>>> PPC?
>>>>>
>>>>> Usually, when I send a patch to qemu-devel, I know who to address to
>>>>> increase chances of it getting committed. For kvm/vnc/block I just CC
>>>>> Anthony, for Audio I just CC malc, etc.
>>>>>
>>>>
>>>> And who can increase chances of getting committed for a scsi-related
>>>> patch?
>>>> I sent a patch on November, the 10th
>>>> (http://patchwork.ozlabs.org/patch/38100/),
>>>> and it looks like it was just ignored.
>>>>
>>>
>>> It's still whitespace damaged.  Attaching a second copy as an
>>> application/octet does not make the situation any better.  Take the time to
>>> send the patch properly and someone will take the time to review/apply it.
>>
>> I thought attaching a second copy were the way to send the patch properly.
>> Is the proper way described somewhere?
>
> From experience the easiest for everyone (at least the readers) is git-format-patch and git-send-email.

If only everything was as easy as it sounds. Unfortunately
git-send-email was for long time unavailable to Windows users and even
now it is barely usable and hard to configure. TortoiseGit once again
doesn't work because of the changed setting on the nongnu.org mail
server... For me it is never-ending battle, instead of working on QEMU
I have to "fix" the GIT tools to send the patches properly each time I
want to send a patch.

Best regards,
Filip Navara

  reply	other threads:[~2009-12-03  9:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 11:47 [Qemu-devel] Unclear committer situation Alexander Graf
2009-12-01 18:51 ` Anthony Liguori
2009-12-01 19:21   ` Blue Swirl
2009-12-01 21:08     ` Anthony Liguori
2009-12-01 22:49   ` Alexander Graf
2009-12-02 11:18     ` andrzej zaborowski
2009-12-02 11:24       ` Alexander Graf
2009-12-02 12:38         ` Avi Kivity
2009-12-02 11:31   ` Riku Voipio
2009-12-03 14:04     ` Anthony Liguori
2009-12-02  8:26 ` Aurelien Jarno
2009-12-02  8:37   ` Alexander Graf
2009-12-02  8:46     ` Aurelien Jarno
2009-12-02  8:54       ` Alexander Graf
2009-12-02 21:09         ` Jan-Simon Möller
2009-12-02  9:08     ` Avi Kivity
2009-12-02  8:45   ` malc
2009-12-02 15:33 ` Artyom Tarasenko
2009-12-02 18:31   ` [Qemu-devel] " Jan Kiszka
2009-12-02 18:48     ` Artyom Tarasenko
2009-12-03 10:20       ` Michael S. Tsirkin
2009-12-03 13:10         ` andrzej zaborowski
2009-12-02 21:18     ` Anthony Liguori
2009-12-03 10:07       ` Artyom Tarasenko
2009-12-02 18:40   ` [Qemu-devel] " Anthony Liguori
2009-12-02 18:53     ` Artyom Tarasenko
2009-12-02 18:56       ` Alexander Graf
2009-12-03  9:44         ` Filip Navara [this message]
2009-12-03 14:19           ` Anthony Liguori
2009-12-02 19:12       ` Anthony Liguori
2009-12-03  9:20         ` Riku Voipio
2009-12-03 12:56         ` Carl-Daniel Hailfinger
2009-12-03 14:40           ` [Qemu-devel] " Michael S. Tsirkin
2009-12-05  0:25 ` [Qemu-devel] " Isaku Yamahata

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=5b31733c0912030144n6e615cd0ue20ad31652adeda8@mail.gmail.com \
    --to=filip.navara@gmail.com \
    --cc=agraf@suse.de \
    --cc=atar4qemu@googlemail.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 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).