From: Jiri Slaby <jslaby@suse.cz>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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 10:40:56 +0100 [thread overview]
Message-ID: <50ACA1A8.1030307@suse.cz> (raw)
In-Reply-To: <CAB=NE6X9z5YEPD5avSkYd6Ayc90kHF4+b1Vjfw8cvZ3A0gwXOQ@mail.gmail.com>
On 11/21/2012 02:13 AM, Luis R. Rodriguez wrote:
> Ah so keep the original in place to let references to the original in
> whatever way those may exist to keep pointing but promote new usage to
> a copy and.. perhaps refer to the new copy in master, or just leave
> that in place as is?
It depends if they really want to have the same thing we do. I.e. don't
they want to rephrase the document a bit? If so, there is no point of
linking the document at all.
If no, we can create a separate document from that in the kernel so that
we allow people to link that at some fixed version using git commit SHA.
This can be done easily doing a link to git.kernel.org.
The link to git.kernel.org might seem to be long. One can create a
dynamic helper on some web like signed-off-by.cgi?id=SHA and it will
return that document in that version. (It will redirect basically.)
regards,
--
js
suse labs
next prev parent reply other threads:[~2012-11-21 9:41 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
2012-11-21 1:13 ` Luis R. Rodriguez
2012-11-21 9:40 ` Jiri Slaby [this message]
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=50ACA1A8.1030307@suse.cz \
--to=jslaby@suse.cz \
--cc=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