From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Mike Belopuhov <mike.belopuhov@esdenera.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
keir@xen.org, Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] Add missing license and copyright statements to public interface headers.
Date: Tue, 22 Sep 2015 09:00:07 -0400 [thread overview]
Message-ID: <20150922130007.GA24845@l.oracle.com> (raw)
In-Reply-To: <20150922114213.GA6257@kemushi.esdenera.com>
On Tue, Sep 22, 2015 at 01:42:14PM +0200, Mike Belopuhov wrote:
> On Fri, Sep 18, 2015 at 10:13 -0400, Konrad Rzeszutek Wilk wrote:
> > On Fri, Sep 18, 2015 at 08:00:28AM -0400, Boris Ostrovsky wrote:
> > >
> > >
> > > On 09/18/2015 04:44 AM, Ian Campbell wrote:
> > > >On Thu, 2015-09-17 at 13:53 +0200, Mike Belopuhov wrote:
> > > >
> > > >A few words here about the methodology you used to determine the names to
> > > >use would be useful to people looking back on this stuff in the future.
> > > >
> > > >Also it would be sensible to CC everyone whose name you are adding. I've
> > > >added Keir since you already Ccd Boris and I didn't see any other names
> > > >after a quick glance.
> > >
> > > For changes that include my name (pmu files)
> > > Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> >
> > Nack. Sorry Boris.
> >
> > Let me send an email to legal to make sure I am not spouting
> > nonsense. But in the meantime my understanding is that:
> >
> > Copyright (c) 2015 X,Y
> >
> > means that the copyright (ownership of intellectual property)
> > is owned by both X and Y.
> >
> > However we (Boris, and me) both signed this fancy document saying
> > that any work we do is owned by Oracle. It is OK to state
> > the authorship, but the ownership is Oracle's.
> >
> > If it was
> >
> > Copyright (c) 2015 X
> >
> > Author: Y
> >
> > Then that is OK.
>
> Hi Konrad,
>
> Any luck getting this sorted out?
Yes.
Copyright (c) 2015 Oracle and/or its affiliates. All rights reserved.
And no authorship.
>
> Regards,
> Mike
>
> > >
> > > Not sure about format --- files in public directory largely use the same
> > > format as what Mike is suggesting here but most of newer files do what
> > > Konrad said (i.e. "Author" on a separate line).
> > >
> > > We will also want to apply similar patch to Linux tree (once this is done).
> > > Mike, do you mind doing it too?
> > >
> > > -boris
> > >
next prev parent reply other threads:[~2015-09-22 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 11:53 [PATCH] Add missing license and copyright statements to public interface headers Mike Belopuhov
2015-09-17 18:52 ` Konrad Rzeszutek Wilk
2015-09-18 8:44 ` Ian Campbell
2015-09-18 12:00 ` Boris Ostrovsky
2015-09-18 14:13 ` Konrad Rzeszutek Wilk
2015-09-22 11:42 ` Mike Belopuhov
2015-09-22 13:00 ` Konrad Rzeszutek Wilk [this message]
2015-09-22 13:58 ` Mike Belopuhov
-- strict thread matches above, loose matches on Subject: below --
2015-09-22 14:02 Mike Belopuhov
2015-09-24 10:45 ` Ian Campbell
2015-09-24 13:17 ` Boris Ostrovsky
2015-09-24 15:04 ` Konrad Rzeszutek Wilk
2015-09-24 16:06 ` Wei Liu
2015-09-25 7:12 ` Jan Beulich
2015-09-28 9:24 ` Mike Belopuhov
2015-09-29 12:03 ` Mike Belopuhov
2015-09-29 12:23 ` Andrew Cooper
2015-09-29 13:34 ` Mike Belopuhov
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=20150922130007.GA24845@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=keir@xen.org \
--cc=mike.belopuhov@esdenera.com \
--cc=xen-devel@lists.xen.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 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).