From: Linus Torvalds <torvalds@osdl.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
Date: Mon, 23 May 2005 07:27:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0505230723170.2307@ppc970.osdl.org> (raw)
In-Reply-To: <20050523040905.GH18600@alpha.home.local>
On Mon, 23 May 2005, Willy Tarreau wrote:
>
> 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 ?
This is one reason I wanted to avoid the 1.0->1.1 change.
I think that if somebody really cares about the version, the above is
certainly acceptable.
In general, I'd personally not use it, and it seems pointless. If we make
some _real_ changes to the DCO that really matter rather than the 1.0->1.1
thing that I'd consider "obvious clarifications", we'll probably have to
change the sign-off.
As it is, I think we should just make the change very public and let
people know about it, and go with it, because quite frankly, even if
somebody claims that they didn't know about the new version of the DCO,
he'd have to be crazy to claim that he didn't know Linux was public and
that the resulting sign-off is public too, so I see it as a "comfort
level" thing, not anything fundamental.
(And note that even the "comfort level" is not for the people doing the
sign-off, but for the person _receiving_ the sign-off).
Linus
next prev parent reply other threads:[~2005-05-23 14:26 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 ` 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
2005-05-23 14:27 ` Linus Torvalds [this message]
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=Pine.LNX.4.58.0505230723170.2307@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®