All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: pkrempa@redhat.com, marcel.a@redhat.com, libvir-list@redhat.com,
	hutao@cn.fujitsu.com, qemu-devel@nongnu.org, armbru@redhat.com,
	rhod@redhat.com, kraxel@redhat.com,
	Paolo Bonzini <pbonzini@redhat.com>,
	lcapitulino@redhat.com, Laszlo Ersek <lersek@redhat.com>,
	afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 3/3] pvpanic: rename to isa-pvpanic
Date: Sun, 25 Aug 2013 13:29:24 +0300	[thread overview]
Message-ID: <20130825102924.GD32448@redhat.com> (raw)
In-Reply-To: <87k3jdsm8s.fsf@codemonkey.ws>

On Thu, Aug 22, 2013 at 11:50:43AM -0500, Anthony Liguori wrote:
> Laszlo Ersek <lersek@redhat.com> writes:
> 
> > On 08/21/13 19:06, Paolo Bonzini wrote:
> >> Il 21/08/2013 19:07, Michael S. Tsirkin ha scritto:
> >
> >>> NACK
> >> 
> >> You know that a single developer's NACK counts nothing (it can be you,
> >> it can be me), don't you?
> >
> > going meta...
> >
> > What's this?
> >
> > All I know (... I think I know) about patch acceptance is that Anthony
> > prefers to have at least one R-b. As far as I've seen this is not a hard
> > requirement (for example, maintainers sometimes send unreviewed patches
> > in a pull request, and on occasion they are merged).
> 
> I look very poorly on anyone nacking anything.  I value constructive
> feedback.
> Nacking does not add any value to the conversation.  I admire the fact
> that we've been able to maintain a very high level of conversation over
> the years on qemu-devel and throwing around nacks just lowers the
> overall tone.

In that case, what's a good way to clarify that one is opposed to the
idea, not the implementation?

We have Acked-by: versus Reviewed-by: on the positive side,
and I was looking for something like this on the negative
side.

> 
> If you can't think of anything better to say than NACK, don't even
> bother sending the email in the first place.

I did add motivation too, it was snipped in the response.

> Regards,
> 
> Anthony Liguori
> 
> >
> > No words have been spent on NAKs yet (... since my subscription, that
> > is). Is this stuff formalized somewhere?
> >
> > Sorry for wasting time...
> >
> > Thanks,
> > Laszlo

  reply	other threads:[~2013-08-25 10:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 16:43 [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess Paolo Bonzini
2013-08-21 16:43 ` [Qemu-devel] [PATCH 1/3] vl: allow "cont" from panicked state Paolo Bonzini
2013-08-21 16:43 ` [Qemu-devel] [PATCH 2/3] pc: get rid of builtin pvpanic Paolo Bonzini
2013-08-21 17:03   ` Michael S. Tsirkin
2013-08-21 17:02     ` Paolo Bonzini
2013-08-21 17:07       ` Andreas Färber
2013-08-21 17:04     ` Michael S. Tsirkin
2013-08-21 17:33   ` Michael S. Tsirkin
2013-08-21 16:43 ` [Qemu-devel] [PATCH 3/3] pvpanic: rename to isa-pvpanic Paolo Bonzini
2013-08-21 17:01   ` Michael S. Tsirkin
2013-08-21 17:01     ` Paolo Bonzini
2013-08-21 17:07       ` Michael S. Tsirkin
2013-08-21 17:06         ` Paolo Bonzini
2013-08-21 17:31           ` Michael S. Tsirkin
2013-08-22 12:43           ` Laszlo Ersek
2013-08-22 12:41             ` Paolo Bonzini
2013-08-25 10:44               ` Michael S. Tsirkin
2013-08-22 16:50             ` Anthony Liguori
2013-08-25 10:29               ` Michael S. Tsirkin [this message]
2013-08-21 17:35     ` Andreas Färber
2013-08-21 17:46       ` Paolo Bonzini
2013-08-21 16:48 ` [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess Daniel P. Berrange
2013-08-21 16:51   ` Paolo Bonzini
2013-08-21 16:55     ` Daniel P. Berrange
2013-08-21 16:56       ` Paolo Bonzini
2013-08-21 17:10         ` Eric Blake
2013-08-21 17:11           ` Paolo Bonzini
2013-08-22  9:17         ` Daniel P. Berrange
2013-08-21 17:02     ` Eric Blake
2013-08-21 17:10       ` Paolo Bonzini
2013-08-21 17:26       ` Michael S. Tsirkin
2013-08-21 17:30         ` Paolo Bonzini

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=20130825102924.GD32448@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lersek@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rhod@redhat.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.