Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <mpdesouza@suse.de>
To: Neal Gompa <ngompa@fedoraproject.org>, linux-btrfs@vger.kernel.org
Cc: Omar Sandoval <osandov@fb.com>, David Sterba <dsterba@suse.com>,
	Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>,
	Anand Jain <anand.jain@oracle.com>, Qu Wenruo <wqu@suse.com>,
	Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
	Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: Re: [PATCH 0/1] btrfs-progs: libbtrfsutil: Relicense to LGPLv2.1+
Date: Thu, 18 Mar 2021 08:46:35 -0300	[thread overview]
Message-ID: <eb04926d5961114c0401a87e32eb7c540efbbc82.camel@suse.de> (raw)
In-Reply-To: <20210317200144.1067314-1-ngompa@fedoraproject.org>

On Wed, 2021-03-17 at 16:01 -0400, Neal Gompa wrote:
> This is a patch requesting all substantial copyright owners to sign
> off
> on changing the license of the libbtrfsutil code to LGPLv2.1+ in
> order
> to resolve various concerns around the mixture of code in btrfs-progs
> with libbtrfsutil.
> 
> Each significant (i.e. non-trivial) commit author has been CC'd to
> request their sign-off on this. Please reply to this to acknowledge
> whether or not this is acceptable for your code.
> 
> Neal Gompa (1):
>   btrfs-progs: libbtrfsutil: Relicense to LGPLv2.1+

Acked-by: Marcos Paulo de Souza <mpdesouza@suse.com>

> 
>  libbtrfsutil/COPYING              | 1130 ++++++++++++---------------
> --
>  libbtrfsutil/COPYING.LESSER       |  165 -----
>  libbtrfsutil/btrfsutil.h          |    2 +-
>  libbtrfsutil/btrfsutil_internal.h |    2 +-
>  libbtrfsutil/errors.c             |    2 +-
>  libbtrfsutil/filesystem.c         |    2 +-
>  libbtrfsutil/python/btrfsutilpy.h |    2 +-
>  libbtrfsutil/python/error.c       |    2 +-
>  libbtrfsutil/python/filesystem.c  |    2 +-
>  libbtrfsutil/python/module.c      |    2 +-
>  libbtrfsutil/python/qgroup.c      |    2 +-
>  libbtrfsutil/python/setup.py      |    4 +-
>  libbtrfsutil/python/subvolume.c   |    2 +-
>  libbtrfsutil/qgroup.c             |    2 +-
>  libbtrfsutil/stubs.c              |    2 +-
>  libbtrfsutil/stubs.h              |    2 +-
>  libbtrfsutil/subvolume.c          |    2 +-
>  17 files changed, 495 insertions(+), 832 deletions(-)
>  delete mode 100644 libbtrfsutil/COPYING.LESSER
> 


  parent reply	other threads:[~2021-03-18 11:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 20:01 [PATCH 0/1] btrfs-progs: libbtrfsutil: Relicense to LGPLv2.1+ Neal Gompa
2021-03-17 20:01 ` [PATCH 1/1] " Neal Gompa
2021-03-17 21:23 ` [PATCH 0/1] " Omar Sandoval
2021-03-18  0:19 ` misono.tomohiro
2021-03-18  0:32 ` Qu Wenruo
2021-03-18 15:47   ` David Sterba
2021-03-18 11:46 ` Marcos Paulo de Souza [this message]
2021-03-18 12:50 ` Anand Jain
2021-03-23  0:57 ` Zygo Blaxell
2021-03-23 15:50 ` David Sterba
2021-03-30 13:21   ` Neal Gompa
2021-04-16 19:05     ` David Sterba

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=eb04926d5961114c0401a87e32eb7c540efbbc82.camel@suse.de \
    --to=mpdesouza@suse.de \
    --cc=anand.jain@oracle.com \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=misono.tomohiro@jp.fujitsu.com \
    --cc=mpdesouza@suse.com \
    --cc=ngompa@fedoraproject.org \
    --cc=osandov@fb.com \
    --cc=wqu@suse.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