All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Drake <dsd@laptop.org>
Cc: mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	dilinger@queued.net, pgf@laptop.org
Subject: Re: [PATCH v4] x86, olpc: add debugfs interface for EC commands
Date: Mon, 26 Mar 2012 15:53:59 -0700	[thread overview]
Message-ID: <20120326155359.e5092006.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAMLZHHSD8eRd17NyUb=Druj==4Eh+XtY=86vGQUGU1fiPMcMNg@mail.gmail.com>

On Mon, 26 Mar 2012 16:45:10 -0600
Daniel Drake <dsd@laptop.org> wrote:

> On Mon, Mar 26, 2012 at 3:29 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > s/fix/break/? __"Originally-from" is not a recognised tag. __If this code
> > is based upon an earlier version from Paul then Signed-off-by: is
> > correct.
> >
> > What's going on here? __What are you trying to communicate?
> 
> I'm trying to take Ingo's suggestion, in the thread "[patch 1/8] x86,
> olpc: add debugfs interface for EC commands" he wrote:
> 
> ====
> This is not a valid signoff sequence - the 'From: ' author of
> the patch must be the first SOB line.
> 
> The way to do this is either to have a:
> 
>  From: Paul Fox <pgf@laptop.org>
> 
> or to covert Paul Fox's SOB to a credit line, such as:
> 
>  Originally-from: Paul Fox <pgf@laptop.org>
> ====
> 
> The original code was from Paul Fox. I changed it somewhat
> significantly, and Paul approves of the end result.
> Can someone suggest a way of expressing this, including tag ordering,
> that will be accepted by all parties?  :)

From: Daniel Drake <dsd@laptop.org>

....

The original code was from Paul Fox.  I changed it somewhat
significantly, and Paul approves of the end result.

Signed-off-by: Paul Fox <pgf@laptop.org>
Signed-off-by: Daniel Drake <dsd@laptop.org>


If I see a changelog like that, I will assume that Paul is OK with you
having the primary authorship (although some suspicion remains ;)). 
Especially when both individuals are from the same organization.

You could swap the order of the Signed-off-by: lines, but the ordering
of those lines isn't at all a reliable indication of anything.  So
nobody should actually *use* the ordering for any purpose.  It is best
to explicitly clarify these things in the changelog text.


  parent reply	other threads:[~2012-03-26 22:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 18:07 [PATCH v4] x86, olpc: add debugfs interface for EC commands Daniel Drake
2012-03-26 21:29 ` Andrew Morton
2012-03-26 21:31   ` H. Peter Anvin
2012-03-26 21:51     ` Andrew Morton
2012-03-27 16:07       ` Matthew Garrett
2012-03-27 16:18         ` Valdis.Kletnieks
2012-03-26 22:13   ` Paul Fox
2012-03-26 22:45   ` Daniel Drake
2012-03-26 22:47     ` H. Peter Anvin
2012-03-26 23:05       ` Andrew Morton
2012-03-26 22:53     ` Andrew Morton [this message]
2012-03-26 23:57       ` Andres Salomon
2012-03-26 23:14   ` Ingo Molnar
2012-03-26 23:23     ` Andrew Morton
2012-03-26 23:49       ` Ingo Molnar
2012-03-27  4:37       ` Joe Perches

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=20120326155359.e5092006.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dilinger@queued.net \
    --cc=dsd@laptop.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pgf@laptop.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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.