All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Unclear committer situation
Date: Wed, 02 Dec 2009 19:31:56 +0100	[thread overview]
Message-ID: <4B16B29C.40104@siemens.com> (raw)
In-Reply-To: <fb8d4f70912020733h67de2f02o9946dec71a7108b0@mail.gmail.com>

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.
> 

Patch is line-wrapped (following your link to patchwork makes this obvious).

Note that the merge process can be quite silent. Hearing nothing for a
while (some weeks) may also mean that your patch suddenly pops up in the
tree - given it's clean and no one complained.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-12-02 18:32 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   ` Jan Kiszka [this message]
2009-12-02 18:48     ` [Qemu-devel] " 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
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=4B16B29C.40104@siemens.com \
    --to=jan.kiszka@siemens.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 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.