From: "Jakub Narębski" <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: What is the status of GSoC 2022 work on making Git use roaring bitmaps?
Date: Thu, 23 Mar 2023 20:26:11 +0100 [thread overview]
Message-ID: <858rfnb770.fsf@gmail.com> (raw)
Hello,
Could you tell me what is the status of the Abhradeep Chakraborty work
in integrating roaring bitmaps (using CRoaring) in addition to, or
replacing current EWAH bitmaps (using ewok)? The last communication
about this shows that the patches were on the road to being merged in,
see e.g. https://medium.com/@abhra303/gsoc-final-report-feaaacfae737 ,
but there is no mention of 'roaring' in Git's code or documentation.
Moreover, there is no proposal to finish this on the GSoC 2023 ideas
page: https://git.github.io/SoC-2023-Ideas/ . Is it because it would be
too small of a project? Or maybe it turned out that roaring bitmaps
were not a good idea - though I haven't found mentions of any benchmarks
of roaring vs EWAH in the mailing list archives? Or perhaps there is no
one to mentor this proposal?
Regards,
--
Jakub Narębski
next reply other threads:[~2023-03-23 19:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 19:26 Jakub Narębski [this message]
2023-03-23 20:26 ` What is the status of GSoC 2022 work on making Git use roaring bitmaps? Taylor Blau
2023-03-23 22:01 ` Jakub Narębski
2023-03-24 3:48 ` Abhradeep Chakraborty
2023-03-25 17:40 ` Jakub Narębski
2023-07-31 17:46 ` Han-Wen Nienhuys
2023-07-31 20:18 ` Taylor Blau
2023-08-01 11:26 ` Han-Wen Nienhuys
2023-08-01 11:34 ` Jakub Narębski
2023-08-01 11:54 ` Han-Wen Nienhuys
2023-08-01 13:17 ` Jakub Narębski
2023-08-01 17:33 ` Taylor Blau
2023-08-01 17:43 ` Jakub Narębski
2023-08-01 17:31 ` Taylor Blau
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=858rfnb770.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=git@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.
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).