From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>,
"Taylor Blau" <me@ttaylorr.com>
Subject: Re: Can I use CRoaring library in Git?
Date: Sun, 17 Jul 2022 17:55:32 +0530 [thread overview]
Message-ID: <e574ac20-c287-c395-5bc3-b481d81764c7@gmail.com> (raw)
In-Reply-To: <CAPOJW5zNsETYwD=MXCFLn91qaemgooPN-JB1sx7KagkKxOXTnQ@mail.gmail.com>
On 16-07-2022 21:56, Abhradeep Chakraborty wrote:
> On Sat, Jul 16, 2022 at 7:50 PM Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>>
>> Another possibility is to get the library to dual-license itself,
>> running "git shortlog -sn" on it it seems it's mainly written by one
>> contributor, with a relatively short tail of others, perhaps they'd be
>> willing to dual-license at the prospect of having git use it?
>
> Kaartic suggested the same and it seems better than the previous one.
>
> As a side note, the current EWAH implementation is also relicensed[1]
> to make it compatible with Git. As these two are mainly written by the
> same person, I think he will help us this time also.
>
The EWAH case is a bit different. The original EWAH implementation
[ewah-cpp] was in C++. It was then ported to C [ewah-c] by Git
contributors [ewah-git]. The ported version has been relicensed under
GPLv2 with Deniel Lemire's permission.
The case with CRoaring is that the implementation already exists in C
[croaring] and that is the one which is licensed under Apache V2. I'm
not sure how relicensing works for already existing code.
I suppose we could enquire Daniel Lemire about using the Apache licensed
code for Git. Let's hope for the best.
[[ References ]]
[ewah-cpp]: https://github.com/lemire/EWAHBoolArray
[ewah-c]: https://github.com/vmg/libewok
[ewah-git]: The initial commit of 'ewah' directory mentions the
relicensing:
e1273106f6 (ewah: compressed bitmap implementation, 2013-11-14)
[croaring]: https://github.com/RoaringBitmap/CRoaring
> Thanks!
>
> [1] https://github.blog/2015-09-22-counting-objects/#footnote-1
--
Sivaraam
next prev parent reply other threads:[~2022-07-17 12:25 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e574ac20-c287-c395-5bc3-b481d81764c7@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=avarab@gmail.com \
--cc=chakrabortyabhradeep79@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).