All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
	George Dunlap <George.Dunlap@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [PATCH] Remove ambiguities in the COPYING file; add CONTRIBUTING file
Date: Fri, 12 Aug 2016 09:15:48 +0000	[thread overview]
Message-ID: <D3D351E6.2CAAD%lars.kurth@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1608111147330.25028@sstabellini-ThinkPad-X260>



On 11/08/2016 19:57, "Stefano Stabellini" <sstabellini@kernel.org> wrote:

>On Thu, 11 Aug 2016, George Dunlap wrote:
>> On 11/08/16 01:51, Stefano Stabellini wrote:
>> > On Wed, 10 Aug 2016, Lars Kurth wrote:
>>
>> >> diff --git a/CONTRIBUTING b/CONTRIBUTING
>> >> new file mode 100644
>> >> index 0000000..7af13c4
>> >> --- /dev/null
>> >> +++ b/CONTRIBUTING
>> >> @@ -0,0 +1,210 @@
>> >> +
>> >> +CONTRIBUTING
>> >> +============
>> >> +
>> >> +INBOUND LICENSE
>> >> +---------------
>> >> +
>> >> +Contributions are governed by the license that applies to relevant
>> >> +specific file or by the license specified in the COPYING file, that
>> >              ^files
>> 
>> I think "file" is better here, as the license is on a file-by-file
>> basis, not on a whole contribution basis.  That is, if your contribution
>> changes a BSD file and a GPLv2 file in a single series (or a single
>> patch), then the changes to the BSD file are goverened by the BSD
>> licence, and the changes to the GPLv2 file are governed by the GPLv2.
>
>OK, I understand the intention behind that sentence but it sounds odd to
>me (possibly because I am not a native English speaker so if it is
>technically correct, you might want to ignore my comment).
>Shouldn't it be:
>
>    to _a_ relevant specific file

I will fix this. I think probably _the_ instead of _a_ is better. Next
revision coming.
Lars

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-12  9:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 11:30 [PATCH] Remove ambiguities in the COPYING file; add CONTRIBUTING file Lars Kurth
2016-08-11  0:51 ` Stefano Stabellini
2016-08-11  9:49   ` George Dunlap
2016-08-11 10:52     ` Lars Kurth
2016-08-11 18:57     ` Stefano Stabellini
2016-08-12  9:15       ` Lars Kurth [this message]
2016-08-11 10:39   ` Lars Kurth
2016-08-11 18:59     ` Stefano Stabellini
2016-08-12  9:13       ` Lars Kurth
2016-08-12 21:45         ` Stefano Stabellini
2016-08-11  9:56 ` George Dunlap
2016-08-11 11:05   ` Lars Kurth
2016-08-11 13:33     ` George Dunlap

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=D3D351E6.2CAAD%lars.kurth@citrix.com \
    --to=lars.kurth@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=committers@xenproject.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.