From: Theodore Tso <tytso@mit.edu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, bcollins@ubuntu.com, akpm@osdl.org
Subject: Re: reviewing Ubuntu kernel patches
Date: Fri, 16 Jun 2006 10:03:34 -0400 [thread overview]
Message-ID: <20060616140334.GA24491@thunk.org> (raw)
In-Reply-To: <44924425.1040501@oracle.com>
On Thu, Jun 15, 2006 at 10:39:49PM -0700, Randy Dunlap wrote:
> Certainly a good question IMO. If Andrew or Linus knows whether
> I need to add my Signed-off-by, I'll be glad to listen.
> (That's not a general call for opinions.)
If you're submitting the patch, then surely you need to add your
Signed-off-by:, since you're asserting either (b) or (c):
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
We've gotten into the habit of assuming the Signed-off-by: also has
the meaning of "I vouch for it from technical point of view", but
really, that's presumably true since otherwise you wouldn't have
e-mailed it to Andrew or Linus. The original meaning of the
Signed-off-by: is in the Developer's Certificate of Origin
statement...
- Ted
next prev parent reply other threads:[~2006-06-16 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 23:22 reviewing Ubuntu kernel patches Randy Dunlap
2006-06-15 0:06 ` Ben Collins
2006-06-15 15:42 ` Arjan van de Ven
2006-06-16 5:39 ` Randy Dunlap
2006-06-16 14:03 ` Theodore Tso [this message]
2006-06-21 17:38 ` Adrian Bunk
2006-06-21 20:25 ` Andrew Morton
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=20060616140334.GA24491@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bcollins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 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.