From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Streamlining Developer's Certificate of Origin, Signed-off-by tag
Date: Wed, 21 Nov 2012 00:10:43 +0000 [thread overview]
Message-ID: <20121121001043.7e1a68df@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAB=NE6UnA2o7ur+0WGouJR984LqtdTYey41XzQCvAw1djhkOkA@mail.gmail.com>
> Not just a separate document but project / github / whatever given
> that other projects are referring to it now, and we stand to gain more
> in the community by streamlining it more and making it ubiquitous.
Cutting and pasting it somewhere works (subject to whatever licensing
it may have itself), as does having a list and a location for a copy, but
you still want it in the tree proper.
There's a reason that lawyers copy documents into other documents rather
than doing late dynamic binding - you want to be sure that what you
reference is the *exact* text that is valid for this case.
If you have a single master official copy and a link then you break all
that and you'd have to have everyones consensus and planning to change a
word of it.
Alan
next prev parent reply other threads:[~2012-11-21 0:05 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
2012-11-20 22:08 ` Arend van Spriel
2012-11-20 22:21 ` Luis R. Rodriguez
2012-11-21 0:10 ` Alan Cox [this message]
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=20121121001043.7e1a68df@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arend@broadcom.com \
--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