public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Streamlining Developer's Certificate of Origin, Signed-off-by tag
Date: Tue, 20 Nov 2012 21:16:34 +0000	[thread overview]
Message-ID: <20121120211634.11513416@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAB=NE6WTFv80w6bkQNqaAG69CADmdiqa-tLKD9s=h_p+1D92tQ@mail.gmail.com>

On Tue, 20 Nov 2012 12:59:40 -0800
"Luis R. Rodriguez" <mcgrof@do-not-panic.com> wrote:

> So it turns out everyone and their mother's attorneys love the
> Signed-off-by tag and its definition as explained on the Linux kernel
> under the Developer's Certificate of Origin. Its to the extent other
> projects have picked it up and started documenting their own
> documentation for submitting patches to embrace the same definition,
> some without knowing what they were doing, some knowingly and
> rightfully doing so. I think it'd be good to see more embracement of
> the tag but to help do this it occurs to me perhaps it'd be good to
> treat  the 'Developer's Certificate of Origin' as a standalone
> document that we can reference independently, and then have the kernel
> itself refer to it. That is, provide a unified easy way to refer to
> the practice for requiring the SOB tag and what it means.
> 
> Thoughts?

Nobody is stopping you putting a copy on a web site.


  reply	other threads:[~2012-11-20 21:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 20:59 Streamlining Developer's Certificate of Origin, Signed-off-by tag Luis R. Rodriguez
2012-11-20 21:16 ` Alan Cox [this message]
2012-11-20 22:08   ` Arend van Spriel
2012-11-20 22:21     ` Luis R. Rodriguez
2012-11-21  0:10       ` Alan Cox
2012-11-21  1:13         ` Luis R. Rodriguez
2012-11-21  9:40           ` Jiri Slaby
2012-11-21 14:54           ` Alan Cox
2012-11-24 14:25         ` W. Trevor King
2012-12-08 16:22         ` W. Trevor King
2013-02-26 21:37           ` Luis R. Rodriguez

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=20121120211634.11513416@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=torvalds@linux-foundation.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