All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs-progs relicensing update
Date: Tue, 25 Mar 2014 13:57:23 -0700	[thread overview]
Message-ID: <5331EDB3.3080903@redhat.com> (raw)

Hi all,

In the process to relicense btrfs-progs to LGPLv2.1[1], we have 40 of 
114 approvals so far. I have sent mass-emails to everyone with more than 
1 commit, and am now sending individual emails down the list to people I 
haven't heard from.

(I'm waiting to tackle the single-commit people until we get all the 
more major contributors.)

Here's progress so far:

https://docs.google.com/spreadsheet/ccc?key=0AuE18RMM7JeKdFF4OVdsYU9GVmVEOGNKajdPYThHSWc&usp=sharing

If you are a contributor and haven't yet given your ok, please feel free 
to reply to me off-list with this text:

-I grant permission to re-license my contributed code to btrfs-progs
under the GNU LGPLv2.1 license.-

and I'll be sure to count you :-)

Thanks -- Regards -- Andy

[1] this is to allow btrfs-progs to be used as a library without 
licensing considerations.

                 reply	other threads:[~2014-03-25 20:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5331EDB3.3080903@redhat.com \
    --to=agrover@redhat.com \
    --cc=linux-btrfs@vger.kernel.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.