qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Amit Shah <amit.shah@redhat.com>,
	Mark McLoughlin <markmc@redhat.com>,
	Bernhard Kauer <kauer@os.inf.tu-dresden.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained?
Date: Thu, 10 Sep 2009 19:35:43 +0300	[thread overview]
Message-ID: <4AA92ADF.80003@redhat.com> (raw)
In-Reply-To: <4AA927D8.7000900@codemonkey.ws>

On 09/10/2009 07:22 PM, Anthony Liguori wrote:
>> You certainly shouldn't ack patches you don't commit!
>
>
> But most spend time in staging.

What's the percentage of patches that make it to master?  For me it's 
 >90%.  If it's too low we nned to fix that.

>
> Acking patches that go to master, that's perfectly fine to do. 

I think that's too late, especially as it often takes a week for master 
to be pushed.  To a submitter, an ack means "no further action is 
required from you at this time" and it's good to provide it as early as 
possible.

> The qemu-commits list does that and should CC the author directly so 
> this should be happening. 

It's too late, and doesn't help others who have an interest in the patch.

> It's acking things that go into staging that I think would be 
> difficult and not necessarily productive.

That is what I do and it doesn't seem to be troublesome.  If I drop a 
patch from a queue I explicitly unack it.

>
>>> This is goofy and is caused by improper patch submission.  But when 
>>> people quote email threads in a commit message, I don't remove 
>>> them.  It don't see it as a problem.
>>
>> From long experience, most commit messages need to be edited.  People 
>> rarely write commit messages that can be understood a year later, and 
>> they don't know how 'git am' works.
>
> I don't like editing patches.  I think it's unfair to the submitter to 
> change their patch underneath of them.  I'd suggest providing feedback 
> on the list to people who write bad commit messages and ask them to 
> write better ones.  I try to limit the changes I make to resolving 
> merge conflicts.

Editing the commit log is not changing the patch.  I doubt you'll be 
able to get better commit messages - submitters have more immediate 
perspectives than maintainers (should have).  I always try to make the 
log make sense a year from now (the code may change, but the commit log 
won't).

Unfairly picking on Mark (who usually writes truly excellent changelogs, 
but this one is such a gem):

> Subject: [Qemu-devel] [PATCH 01/19] Suppress more more kraxelism
>
> Let's kick off this series with some of the more critical fixes.
>
> Signed-off-by: Mark McLoughlin<markmc@redhat.com>
>    

What would you be thinking hunting the commit log for some change and 
coming up with this?

(Mark, apologies for picking on you, it's truly unfair of me, but I 
can't help it)

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  reply	other threads:[~2009-09-10 16:35 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02  7:49 [Qemu-devel] [PATCH] [RESEND] RTC polling mode broken Bernhard Kauer
2009-09-09 12:18 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Bernhard Kauer
2009-09-09 12:23   ` Amit Shah
2009-09-09 12:58     ` Bernhard Kauer
2009-09-09 12:25   ` Kevin Wolf
2009-09-09 13:00   ` Anthony Liguori
2009-09-09 13:26     ` Gleb Natapov
2009-09-09 13:45       ` Anthony Liguori
2009-09-09 14:31       ` Avi Kivity
2009-09-09 13:34     ` Bernhard Kauer
2009-09-10  7:03     ` Amit Shah
2009-09-10  7:56       ` Reimar Döffinger
2009-09-10 10:08         ` Amit Shah
2009-09-10 11:47           ` Luiz Capitulino
2009-09-10 12:01             ` [Qemu-devel] QEMU patch management Amit Shah
2009-09-10 12:29               ` [Qemu-devel] " Luiz Capitulino
2009-09-10 12:51                 ` Reimar Döffinger
2009-09-10 13:11                   ` Luiz Capitulino
2009-09-10 17:24                     ` Reimar Döffinger
2009-09-10 13:58             ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Anthony Liguori
2009-09-10 13:56       ` Anthony Liguori
2009-09-10 14:04         ` Amit Shah
2009-09-10 14:12           ` Anthony Liguori
2009-09-10 15:15             ` Amit Shah
2009-09-10 14:38         ` Avi Kivity
2009-09-10 15:54           ` Anthony Liguori
2009-09-10 16:09             ` Avi Kivity
2009-09-10 16:22               ` Anthony Liguori
2009-09-10 16:35                 ` Avi Kivity [this message]
2009-09-10 16:38                   ` Anthony Liguori
2009-09-10 16:46                     ` Avi Kivity
2009-09-10 17:19                       ` Reimar Döffinger
2009-09-11 12:39                         ` Amit Shah
2009-09-12  5:55                         ` Blue Swirl
2009-09-13 15:44                           ` Avi Kivity
2009-09-13 16:30                             ` Blue Swirl
2009-09-11  7:06                     ` Gerd Hoffmann
2009-09-10 18:29                   ` Mark McLoughlin
2009-09-10 18:40                     ` Avi Kivity
2009-09-10 19:31                       ` Anthony Liguori
2009-09-13 15:49                         ` Avi Kivity
2009-09-10 20:36                       ` Mark McLoughlin
2009-09-13 16:19                         ` Avi Kivity
2009-09-14  7:49                           ` Mark McLoughlin
2009-09-14  7:59                             ` Avi Kivity
2009-09-10 18:59                     ` Reimar Döffinger
2009-09-10 16:05           ` Anthony Liguori
2009-09-10 16:14             ` Avi Kivity
2009-09-11  9:16           ` [Qemu-devel] commit e09a5267 (was: [PATCH] [RESEND2] Qemu unmaintained?) Jan Kiszka
2009-09-11 12:56             ` [Qemu-devel] Re: commit e09a5267 Anthony Liguori
2009-09-11 13:04               ` Jan Kiszka

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=4AA92ADF.80003@redhat.com \
    --to=avi@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kauer@os.inf.tu-dresden.de \
    --cc=markmc@redhat.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).