From: Theodore Tso <tytso@mit.edu>
To: Coly Li <coyli@suse.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] removing e2fsprogs compiling warnings
Date: Sat, 4 Aug 2007 10:56:20 -0400 [thread overview]
Message-ID: <20070804145620.GA16163@thunk.org> (raw)
In-Reply-To: <46B417A2.1040201@suse.de>
On Sat, Aug 04, 2007 at 02:07:30PM +0800, Coly Li wrote:
>
> Do you mean "Signed-off-by Coly Li <coyli@suse.de>" ?
> I just though this is used for others to sign my patch :-)
No, it's really bad to add a Signed-off-by for anyone other than
yourself, since it has legal significance. It's something that you
have to do for yourself. :-)
Quoting from SUBMITTING-PATCHES:
The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as a open-source patch. The rules are pretty simple: if you
can certify the below:
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.
(d) 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(s) involved.
then you just add a line saying
Signed-off-by: Random J Developer <random@developer.example.org>
In this case of your gcc -Wall cleanups, the changes involved were
small and probably fell below the threshold of something that could be
protected by copyright --- and I ended up choosing a different way of
cleaning up for one or two of the cleanups anyway. But for anything
non-trivial, these days I am requested a Developers Certification of
Origin.
Regards,
- Ted
next prev parent reply other threads:[~2007-08-04 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 7:18 [PATCH] removing e2fsprogs compiling warnings Coly Li
2007-08-03 22:32 ` Theodore Tso
2007-08-04 6:07 ` Coly Li
2007-08-04 14:56 ` Theodore Tso [this message]
2007-08-05 13:25 ` Coly Li
2007-08-04 6:55 ` Coly Li
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=20070804145620.GA16163@thunk.org \
--to=tytso@mit.edu \
--cc=coyli@suse.de \
--cc=linux-ext4@vger.kernel.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 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.