All of lore.kernel.org
 help / color / mirror / Atom feed
* Signed-off-by
@ 2004-05-24 20:55 Albert Cahalan
  0 siblings, 0 replies; 3+ messages in thread
From: Albert Cahalan @ 2004-05-24 20:55 UTC (permalink / raw)
  To: linux-kernel mailing list; +Cc: torvalds

Linus Torvalds writes:

> (Seriously, while nobody has actually complained about
> the suggested rules, I don't think anybody should feel
> compelled to do the sign-off before we've had more
> time to let people argue over it. People who feel 
> comfortable with the suggestion are obviously
> encouraged to start asap, though).

I had been hoping someone had just forged your email
address. :-/

The wordy mix-case aspect is kind of annoying, and for
all that we don't get to differentiate actions.
I count:

1. came up with the design ideas
2. wrote the original patch
3. reviewed and passed on
4. modified
5. blindly passed on

Maybe "blindly passed on" needs nothing. So I'm
thinking, if we must bother with all this...

designed:
authored:
reviewed:
modified:

Add "pirated:" if you like, so that searching for
pirated code is easier than checking the evil bit.




^ permalink raw reply	[flat|nested] 3+ messages in thread

* signed-off-by
@ 2005-12-16  7:02 James Harper
  0 siblings, 0 replies; 3+ messages in thread
From: James Harper @ 2005-12-16  7:02 UTC (permalink / raw)
  To: Ian Pratt, xen-devel

> 
> Thanks for the patch, but please can we have a signed-off-by: line
> 

Just for the record, what is the significance of a 'signed-off-by'? Is
it something that hg generates or something that you just manually type
into the email when you submit a patch?

James

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: signed-off-by
@ 2005-12-16  7:45 Ian Pratt
  0 siblings, 0 replies; 3+ messages in thread
From: Ian Pratt @ 2005-12-16  7:45 UTC (permalink / raw)
  To: James Harper, xen-devel

 
> > Thanks for the patch, but please can we have a signed-off-by: line
> > 
> Just for the record, what is the significance of a 
> 'signed-off-by'? Is it something that hg generates or 
> something that you just manually type into the email when you 
> submit a patch?

The signed-off-by: line should be added by hand and is used to track the
provenance of patches. Please see
http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html

Unless a patch is utterly trivial we need it signed off before we can
accept it.

Thanks,
Ian

Developer's Certificate of Origin 1.1 
=====================================

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have
the right to submit it under the open source license indicated in the
file; or

(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; and

(d) In the case of each of (a), (b), or (c), I understand and agree that
this project and the contribution are public and that a record of the
contribution (including all personal information I submit with it,
including my sign-off) is maintained indefinitely and may be
redistributed consistent with this project or the open source license
indicated in the file.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-12-16  7:45 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-24 20:55 Signed-off-by Albert Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2005-12-16  7:02 signed-off-by James Harper
2005-12-16  7:45 signed-off-by Ian Pratt

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.