From: Theodore Tso <tytso@mit.edu>
To: "Brian D. Behlendorf" <behlendorf1@llnl.gov>
Cc: linux-ext4@vger.kernel.org, adilger@clusterfs.com, wartens2@llnl.gov
Subject: Re: e2fsprogs coverity patch <cid-1.diff>
Date: Sat, 10 Feb 2007 08:55:01 -0500 [thread overview]
Message-ID: <20070210135501.GA25607@thunk.org> (raw)
In-Reply-To: <200702100208.l1A28GC2005813@igsi.llnl.gov>
On Fri, Feb 09, 2007 at 06:08:16PM -0800, Brian D. Behlendorf wrote:
> Lawrence Livermore National Labs recently ran the source code
> analysis tool Coverity over the e2fsprogs-1.39 source to see
> if it would identify any significant bugs. The analysis
> turned up 38 mostly minor issues which are enumerated here
> with patches. We went through and resolved these issues
> but would love to see these mostly minor changes reviewed
> and commited upstream.
Hi Brian, please see the SUBMITTING-PATCHES file in the e2fsprogs
repository.
May I assume that you are willing to certify to the Developer's
Certification of Origin 1.1 statement so I can add a:
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
to each of these patches before I check them into the e2fsprogs source
control repository?
In the future, please add the Signed-off-by: line when submitting
patches assuming that you are willing to certify to the DCO 1.1.
Thanks, regards,
- Ted
(The SUBMITTING-PATCHES file has been included below for your
convenience.)
Like the Linux kernel, submitted e2fsprogs patches now require the
following "sign-off" procedure:
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>
next prev parent reply other threads:[~2007-02-10 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 2:08 e2fsprogs coverity patch <cid-1.diff> Brian D. Behlendorf
2007-02-10 13:55 ` Theodore Tso [this message]
2007-02-12 18:23 ` Brian Behlendorf
2007-03-18 13:40 ` Theodore Tso
2007-03-18 17:32 ` Andreas Dilger
2007-03-18 13:55 ` e2fsprogs coverity patch <cid-01.diff> Theodore Tso
2007-03-29 18:07 ` e2fsprogs coverity patch Theodore Tso
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=20070210135501.GA25607@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=behlendorf1@llnl.gov \
--cc=linux-ext4@vger.kernel.org \
--cc=wartens2@llnl.gov \
/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;
as well as URLs for NNTP newsgroup(s).