public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@queued.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daniel Drake <dsd@laptop.org>,
	mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
	x86@kernel.org, linux-kernel@vger.kernel.org, pgf@laptop.org
Subject: Re: [PATCH v4] x86, olpc: add debugfs interface for EC commands
Date: Mon, 26 Mar 2012 16:57:46 -0700	[thread overview]
Message-ID: <20120326165746.30588c55@debxo> (raw)
In-Reply-To: <20120326155359.e5092006.akpm@linux-foundation.org>

On Mon, 26 Mar 2012 15:53:59 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

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


This makes a lot more sense to me (and has been used in the past by
both myself and dsd for OLPC submissions) rather than having a plethora
of machine-parsable tags that no one cares about.  Minus the "approves
of the end result" bit, though, as that's implicit in the SOB line.
There are innumerable possible variants of this (Originally-by,
Co-authored-with, Based-on-code-in-another-project-by,
Written-while-being-whipped-by, and so on).


  reply	other threads:[~2012-03-26 23:57 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
2012-03-26 23:57       ` Andres Salomon [this message]
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=20120326165746.30588c55@debxo \
    --to=dilinger@queued.net \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox