Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Neal Gompa <ngompa@fedoraproject.org>
Cc: linux-btrfs@vger.kernel.org, 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>,
	Sheng Mao <shngmao@gmail.com>
Subject: Re: [PATCH 0/1] btrfs-progs: libbtrfsutil: Relicense to LGPLv2.1+
Date: Tue, 23 Mar 2021 16:50:32 +0100	[thread overview]
Message-ID: <20210323155032.GH7604@twin.jikos.cz> (raw)
In-Reply-To: <20210317200144.1067314-1-ngompa@fedoraproject.org>

On Wed, Mar 17, 2021 at 04:01:43PM -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.

Thanks! I think we have acks for all non-trivial contirbutions. For the
record, the trivial one are:

* dbf60b488e3b ("libbtrfsutil: update btrfs_util_delete_subvolume docs")
  a comment update, clarifying usage

* 2e67bf0ed69d ("btrfs-progs: docs: fix typos in READMEs, INSTALL and * CHANGES")
* b1d39a42a4ef ("btrfs-progs: fix typos in comments")
  treewide comment typo fixes

* 01e35d9f53eb ("btrfs-progs: treewide: Fix missing declarations")
  code changes, but adding static or missing includes

* 9fd37f951be6 ("btrfs-progs: complete the implementation RAID1C34 definitions")
  copied definitions from kernel code

I'm not sure about the commit adding pkg-config spec file, it's not code
but it's beyond what I'd consider trivial. I've added Sheng Mao to CC,
please acknowledge the change.

* 4498fe1a2a7c ("libbtrfsutil: add pkg-config spec file")

I'll update the changelog with all the reasons for relicensing that have
been brought up.

  parent reply	other threads:[~2021-03-23 15:53 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
2021-03-18 12:50 ` Anand Jain
2021-03-23  0:57 ` Zygo Blaxell
2021-03-23 15:50 ` David Sterba [this message]
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=20210323155032.GH7604@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --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=shngmao@gmail.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