qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Josh Durgin" <josh.durgin@inktank.com>,
	qemu-devel@nongnu.org, "Benoît Canet" <benoit@irqsave.net>
Subject: Re: [Qemu-devel] [RFC PATCH v0 1/2] gluster: Change licence to GPLv2+
Date: Mon, 3 Mar 2014 14:21:03 +0530	[thread overview]
Message-ID: <20140303085103.GD20295@in.ibm.com> (raw)
In-Reply-To: <20140130093053.GB8036@stefanha-thinkpad.redhat.com>

On Thu, Jan 30, 2014 at 10:30:53AM +0100, Stefan Hajnoczi wrote:
> On Wed, Jan 29, 2014 at 07:59:55PM +0530, Bharata B Rao wrote:
> > Pipe handling mechanism in gluster driver was based on similar implementation
> > in RBD driver and hence had GPLv2 and associated copyright information.
> > After changing gluster driver to coroutine based implementation, the pipe
> > handling code no longer exists and hence change gluster driver's licence to
> > GPLv2+ and remove RBD copyrights.
> > 
> > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > ---
> >  block/gluster.c | 12 ++----------
> >  1 file changed, 2 insertions(+), 10 deletions(-)
> > 
> > diff --git a/block/gluster.c b/block/gluster.c
> > index a009b15..ba56005 100644
> > --- a/block/gluster.c
> > +++ b/block/gluster.c
> > @@ -3,17 +3,9 @@
> >   *
> >   * Copyright (C) 2012 Bharata B Rao <bharata@linux.vnet.ibm.com>
> >   *
> > - * Pipe handling mechanism in AIO implementation is derived from
> > - * block/rbd.c. Hence,
> > + * This work is licensed under the terms of the GNU GPL, version 2 or later.
> > + * See the COPYING file in the top-level directory.
> >   *
> > - * Copyright (C) 2010-2011 Christian Brunner <chb@muc.de>,
> > - *                         Josh Durgin <josh.durgin@dreamhost.com>
> > - *
> > - * This work is licensed under the terms of the GNU GPL, version 2.  See
> > - * the COPYING file in the top-level directory.
> > - *
> > - * Contributions after 2012-01-13 are licensed under the terms of the
> > - * GNU GPL, version 2 or (at your option) any later version.
> >   */
> >  #include <glusterfs/api/glfs.h>
> >  #include "block/block_int.h"
> 
> I looked at git log -p block/gluster.c and this change seems reasonable,
> but due to the nature of license changes:
> 
> If anyone disagrees and has copyright on part of this file, please speak
> now.

Since nobody has said anything till now, Stefan, would you be taking this
in now ?

Regards,
Bharata.

  reply	other threads:[~2014-03-03  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 14:29 [Qemu-devel] [RFC PATCH v0 0/2] gluster: licence change and cleanups Bharata B Rao
2014-01-29 14:29 ` [Qemu-devel] [RFC PATCH v0 1/2] gluster: Change licence to GPLv2+ Bharata B Rao
2014-01-30  9:30   ` Stefan Hajnoczi
2014-03-03  8:51     ` Bharata B Rao [this message]
2014-01-29 14:29 ` [Qemu-devel] [RFC PATCH v0 2/2] gluster: Remove unused defines and header include Bharata B Rao
2014-01-30  9:31   ` Stefan Hajnoczi
2014-03-03  9:16 ` [Qemu-devel] [RFC PATCH v0 0/2] gluster: licence change and cleanups Stefan Hajnoczi
2014-03-03 10:31   ` Kevin Wolf

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=20140303085103.GD20295@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=benoit@irqsave.net \
    --cc=josh.durgin@inktank.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).