From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: romain@dolbeau.org, qemu-devel@nongnu.org, agraf@suse.de,
"Gabriel L. Somlo" <gsomlo@gmail.com>,
stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] e1000: allow command-line selection of card model
Date: Wed, 21 May 2014 12:25:45 +0300 [thread overview]
Message-ID: <20140521092545.GA19646@redhat.com> (raw)
In-Reply-To: <537C6E0A.4020200@suse.de>
On Wed, May 21, 2014 at 11:12:42AM +0200, Andreas Färber wrote:
> Am 21.05.2014 11:04, schrieb Michael S. Tsirkin:
> > On Wed, May 21, 2014 at 10:40:54AM +0200, Andreas Färber wrote:
> >> Hi,
> >>
> >> Am 20.05.2014 17:05, schrieb Gabriel L. Somlo:
> >>> Allow selection of different card models from the qemu
> >>> command line, to better accomodate a wider range of guests.
> >>>
> >>> Based-on-patch-by: Romain Dolbeau <romain@dolbeau.org>
> >>
> >> If that patch carried a Signed-off-by line, you should retain it.
> >
> > Actually I think that would be confusing. Romain didn't sign off
> > on *this* patch, he signed off on a previous one.
> > A signature by Gabriel indicates Developer's Certificate of Origin 1.1
> > which has an option to incorporate other's work - it
> > does not seem to require signatures by these others.
>
> With the same argument you could drop anyone's Sob you get as a
> maintainer.
I could but it would not be nice to submitters, and it drops useful info
(author's Sob). So if someone thinks there's problematic code here and
comes complaining, we want to be able to say "this code came from XYZ".
> But the purpose of Sob is to track through whose hands a
> patch went, not just who last touched it.
Went untouched or mostly untouched.
Did you bother checking?
I looked and Romain's patch isn't very similar to this one.
> My point here was that Based-on-patch-by is very unusual.
What's the harm?
Gabriel's just being nice and crediting other's work.
> The alternative would be to leave the original From: Romain Dolbeau, his
> Sob, then a [gsomlo: Dropped this, added that] followed by Sob.
>
> Cheers,
> Andreas
That's just asking submitter to do a lot of extra work,
I don't see why would we place roadblocks in submitter's paths
like this. Linux certainly does not and we didn't ask for this
in the past.
Further, the patch author in git will also be the original author then
which is only fair if the patch is changed in very minor ways.
In which case keeping the original Sob around *would* be right.
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-05-21 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 15:05 [Qemu-devel] [PATCH] e1000: allow command-line selection of card model Gabriel L. Somlo
2014-05-21 8:40 ` Andreas Färber
2014-05-21 9:04 ` Michael S. Tsirkin
2014-05-21 9:12 ` Andreas Färber
2014-05-21 9:25 ` Michael S. Tsirkin [this message]
2014-05-21 9:48 ` Andreas Färber
2014-05-21 10:22 ` Michael S. Tsirkin
2014-05-21 10:42 ` Andreas Färber
2014-05-21 12:11 ` Michael S. Tsirkin
2014-05-21 16:02 ` Andreas Färber
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=20140521092545.GA19646@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=gsomlo@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=romain@dolbeau.org \
--cc=stefanha@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 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).