public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
Date: Mon, 23 May 2005 09:21:01 +0200	[thread overview]
Message-ID: <20050523072101.GA23108@alpha.home.local> (raw)
In-Reply-To: <200505230015.48938.dtor_core@ameritech.net>

On Mon, May 23, 2005 at 12:15:48AM -0500, Dmitry Torokhov wrote:
> On Sunday 22 May 2005 23:09, Willy Tarreau wrote:
> > Linus,
> > 
> > On Sun, May 22, 2005 at 03:40:24PM -0700, Linus Torvalds wrote:
> > (...)
> > > -        Developer's Certificate of Origin 1.0
> > > +        Developer's Certificate of Origin 1.1
> > (...)
> > >  then you just add a line saying
> > >  
> > >  	Signed-off-by: Random J Developer <random@developer.org>
> > 
> > Why not change this slightly to something like :
> > 
> >        DCO-1.1-Signed-off-by: Random J Developer <random@developer.org>
> > 
> > which would imply that this person has read (and agreed with) version 1.1 ?
> >
> 
> Ugh, that's ugly, long and redundant. You could have:
> 
>       DCO-m.n: Random J Developer <random@developer.org>
> 
> but it still looks ugly.   

Well, it could be anything ugly. The advantage of keeping the "Signed-off-by"
is that tools which already rely on this string will still find it.

Willy


  reply	other threads:[~2005-05-23  7:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200505220008.j4M08uE9025378@hera.kernel.org>
2005-05-22 11:57 ` When we detect that a 16550 was in fact part of a NatSemi SuperIO chip David Woodhouse
2005-05-22 12:59   ` Russell King
2005-05-22 13:23     ` David Woodhouse
2005-05-22 13:41     ` Russell King
2005-05-22 14:14       ` David Woodhouse
2005-05-22 21:16       ` Alan Cox
2005-05-22 21:50         ` Linus Torvalds
2005-05-22 22:22           ` Alan Cox
2005-05-22 22:40             ` Linus Torvalds
2005-05-22 22:43               ` Alan Cox
2005-05-23  4:09               ` Willy Tarreau
2005-05-23  5:15                 ` Dmitry Torokhov
2005-05-23  7:21                   ` Willy Tarreau [this message]
2005-05-23 14:27                 ` Linus Torvalds
2005-05-22 16:59   ` Linus Torvalds
2005-05-22 17:15     ` David Woodhouse
2005-05-22 18:14     ` Arjan van de Ven
2005-05-22 18:44       ` Russell King
2005-05-22 18:51         ` Arjan van de Ven
2005-05-22 19:03           ` Russell King
2005-05-22 20:31             ` Linus Torvalds
2005-05-22 20:55               ` Brian O'Mahoney
2005-05-22 19:58       ` Brian O'Mahoney
2005-05-22 20:31         ` Lee Revell
2005-05-22 20:48         ` Linus Torvalds

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=20050523072101.GA23108@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=torvalds@osdl.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