From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>,
Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Cc: git <git@vger.kernel.org>, "Taylor Blau" <me@ttaylorr.com>,
"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jakub Narębski" <jnareb@gmail.com>
Subject: Re: Can I use CRoaring library in Git?
Date: Thu, 21 Jul 2022 08:14:23 -0400 [thread overview]
Message-ID: <304fd857-db62-7a1a-a9a9-cbfa93c2a00c@github.com> (raw)
In-Reply-To: <xmqq7d47m1t2.fsf@gitster.g>
On 7/21/2022 2:12 AM, Junio C Hamano wrote:
> Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com> writes:
>
>> On Sat, Jul 16, 2022 at 7:20 PM Abhradeep Chakraborty
>> <chakrabortyabhradeep79@gmail.com> wrote:
>>>
>>> Hello,
>>>
>>> I need the CRoaring[1] library to use roaring bitmaps. But it has
>>> Apache license v2 which is not compatible with GPLv2[2].
>>
>> I have reached out to Daniel and he agreed to make CRoaring
>> dual-licensed under MIT and Apachev2[1].
>> Now, I can use CRoaring, right?
>>
>> [1] https://groups.google.com/g/roaring-bitmaps/c/0d7KoA79k3A
>>
>> Thanks :)
>
> Nice.
Great news! Thanks for reaching out. I'm pleasantly surprised at
the turnaround. Good luck integrating it into the Git codebase!
-Stolee
next prev parent reply other threads:[~2022-07-21 12:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 13:50 Can I use CRoaring library in Git? Abhradeep Chakraborty
2022-07-16 14:16 ` Ævar Arnfjörð Bjarmason
2022-07-16 16:26 ` Abhradeep Chakraborty
2022-07-17 12:25 ` Kaartic Sivaraam
2022-07-17 22:00 ` Junio C Hamano
2022-07-17 22:25 ` Taylor Blau
2022-07-18 8:57 ` Abhradeep Chakraborty
2022-07-25 22:11 ` Taylor Blau
2022-07-17 14:43 ` Derrick Stolee
2022-07-18 11:13 ` Jakub Narębski
2022-07-18 11:38 ` Abhradeep Chakraborty
2022-07-18 13:38 ` Ævar Arnfjörð Bjarmason
2022-07-18 11:48 ` Abhradeep Chakraborty
2022-07-18 12:18 ` Derrick Stolee
2022-07-18 13:15 ` Abhradeep Chakraborty
2022-07-18 21:48 ` brian m. carlson
2022-07-25 22:14 ` Taylor Blau
2022-07-25 22:35 ` rsbecker
2022-07-25 23:37 ` Taylor Blau
2022-07-21 4:07 ` Abhradeep Chakraborty
2022-07-21 6:12 ` Junio C Hamano
2022-07-21 12:14 ` Derrick Stolee [this message]
2022-07-21 13:51 ` Ævar Arnfjörð Bjarmason
2022-07-21 14:57 ` Abhradeep Chakraborty
2022-07-22 11:07 ` Ævar Arnfjörð Bjarmason
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=304fd857-db62-7a1a-a9a9-cbfa93c2a00c@github.com \
--to=derrickstolee@github.com \
--cc=avarab@gmail.com \
--cc=chakrabortyabhradeep79@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.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 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.