All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches
Date: Mon, 20 Apr 2009 12:53:39 -0500	[thread overview]
Message-ID: <49ECB6A3.3010506@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580904200825l5f1de283l98d510148640e762@mail.gmail.com>

Blue Swirl wrote:
> On 4/20/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
>   
>> Blue Swirl wrote:
>>
>>     
>>> Hi,
>>>
>>> I gathered a few common complaints about patch submission, hopefully
>>> not too much affected by my consumption of small amounts of various
>>> alcoholic substances.
>>>
>>> Comments, objections?
>>>  +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 can never be omitted--even for one line fixes.
>>     
>
> I disagree. Changes that are small enough do not create any
> copyrightable material, thus they may come from any source.
>   

It's not just an issue of copyright.  It's also a statement that you are 
allowed to be submitting patches to a given project.  Before DCO, some 
projects used to require forms from employers stating that contributions 
were allowed because some employers have non-compete contracts that 
would prevent an employee from working on a project.

Regards,

Anthony Liguori

  reply	other threads:[~2009-04-20 17:53 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 ` [Qemu-devel] " M. Warner Losh
2009-04-20 14:13 ` Anthony Liguori
2009-04-20 14:31   ` Avi Kivity
2009-04-20 15:25   ` Blue Swirl
2009-04-20 17:53     ` Anthony Liguori [this message]
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=49ECB6A3.3010506@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.