git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 17:14 UTC

What is the status of GSoC 2022 work on making Git use roaring bitmaps?

From
Jakub Narębski <jnareb@gmail.com>
Date
Mar 23, 2023, 19:26 UTC
Message-ID
<858rfnb770.fsf@gmail.com>
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: Taylor Blau
Message 1 of 14 in “What is the status of GSoC 2022 work on making Git use roaring bitmaps?”
  1. Jakub NarębskiMar 23, 2023
  2. Taylor BlauMar 23, 2023
  3. Jakub NarębskiMar 23, 2023
  4. Abhradeep ChakrabortyMar 24, 2023
  5. Jakub NarębskiMar 25, 2023
  6. Han-Wen NienhuysJul 31, 2023
  7. Taylor BlauJul 31, 2023
  8. Han-Wen NienhuysAug 1, 2023
  9. Jakub NarębskiAug 1, 2023
  10. Han-Wen NienhuysAug 1, 2023
  11. Jakub NarębskiAug 1, 2023
  12. Taylor BlauAug 1, 2023
  13. Taylor BlauAug 1, 2023
  14. Jakub NarębskiAug 1, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.