From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, blauwirbel@gmail.com
Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches
Date: Sun, 19 Apr 2009 11:40:23 -0600 (MDT) [thread overview]
Message-ID: <20090419.114023.-1219431309.imp@bsdimp.com> (raw)
In-Reply-To: <f43fc5580904190832g413e67bn494f696a3e3279f4@mail.gmail.com>
In message: <f43fc5580904190832g413e67bn494f696a3e3279f4@mail.gmail.com>
Blue Swirl <blauwirbel@gmail.com> writes:
: +SP2.4: Optionally, the "Signed-off-by:" line may be followed with a
: +line with only "---" and on the following lines, other comments not
: +intended for changelog (for example diffstat, location of a git tree,
: +whether the patch is also directed towards stable tree, witty
: +signature etc.)
: +
: +SP2.5: Exception: For extremely short and trivial patches (one-line
: +fixes etc.), the description and "Signed-off-by:" lines may be
: +omitted, in which case the subject must be appended with the
: +submitter's name in parenthesis
Signed-off-by: is at least an implied contract that the patch
submitted conforms to the Developer's Certificate of Origin 1.1:
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.
At least that's what it means for the Linux world. I believe that
QEMU also follows that, but we should likely make it explicit in this
document.
That's why trivial patches don't necessarily need this: There's no IP
associated with them, so no need to diligently track it.
Warner
next prev parent reply other threads:[~2009-04-19 17:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:32 [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches Blue Swirl
2009-04-19 16:11 ` Avi Kivity
2009-04-19 16:59 ` Blue Swirl
2009-04-19 17:36 ` Andreas Färber
2009-04-20 14:19 ` Anthony Liguori
2009-04-19 17:42 ` M. Warner Losh
2009-04-20 8:32 ` Avi Kivity
2009-04-20 15:22 ` Blue Swirl
2009-04-20 18:16 ` Avi Kivity
2009-04-19 16:48 ` [Qemu-devel] " Jan Kiszka
2009-04-19 17:41 ` M. Warner Losh
2009-04-20 7:43 ` Jan Kiszka
2009-04-20 14:23 ` Anthony Liguori
2009-04-19 17:40 ` M. Warner Losh [this message]
2009-04-20 14:13 ` [Qemu-devel] " Anthony Liguori
2009-04-20 14:31 ` Avi Kivity
2009-04-20 15:25 ` Blue Swirl
2009-04-20 17:53 ` Anthony Liguori
2009-04-20 14:15 ` Anthony Liguori
2009-04-20 15:29 ` Blue Swirl
2009-04-20 15:53 ` Kevin Wolf
2009-04-20 16:10 ` Blue Swirl
2009-04-20 15:54 ` François Revol
2009-04-20 16:13 ` Avi Kivity
2009-04-20 18:02 ` Anthony Liguori
2009-04-20 18:12 ` Avi Kivity
2009-04-20 17:59 ` Anthony Liguori
2009-04-20 17:56 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2009-04-19 21:27 Philippe Waille
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=20090419.114023.-1219431309.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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.