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

Re: [PATCH 3/5] roaring: teach Git to write roaring bitmaps

From
Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Date
Oct 30, 2022, 06:35 UTC
Message-ID
<CAPOJW5z_ZRChNo8PGBmJu=vvjTL2cYL8oTdVwoDRh-UHt2Dy4w@mail.gmail.com>
In-Reply-To
<CAPOJW5yxRETdVk014gQYFud9_Nrt+OQGSVNQ8Pw2wDEMMFMm1Q@mail.gmail.com>
Hello all,

It has been a month since I didn't get involved in any open source contributions (including Git). This is due to the fact that I was focusing more on mastering theories and also that it was a festive month. So, I am now resuming my work. There are many things I have to cover (including this patch series). But before that I want to ask you a question - As you have noticed already, the Roaring library has a lot of styling issues (Moreover it is using C11). So Should I fix all these issues? or Should I make a new library (using Git's compatibility library "git-compat-util.h") by taking CRoaring as a reference? The pros are that it would be easier to format the bitmap library specific files and it can use Git compatible functions.

I would love to hear your opinions. Thanks :)
Previous: Abhradeep ChakrabortyNext: Derrick Stolee
Message 19 of 25 in “[RFC] introduce Roaring bitmaps to Git”
  1. 0/5 [RFC] introduce Roaring bitmaps to GitAbhradeep Chakraborty via GitGitGadget, Sep 19, 2022
  2. 1/5 reachability-bitmaps: add CRoaring library to GitAbhradeep Chakraborty via GitGitGadget, Sep 19, 2022
  3. 4/5 roaring: introduce a new config option for roaring bitmapsAbhradeep Chakraborty via GitGitGadget, Sep 19, 2022
  4. 2/5 roaring.[ch]: apply Git specific changes to the roaring APIAbhradeep Chakraborty via GitGitGadget, Sep 19, 2022
  5. 3/5 roaring: teach Git to write roaring bitmapsAbhradeep Chakraborty via GitGitGadget, Sep 19, 2022
  6. 5/5 roaring: teach Git to read roaring bitmapsAbhradeep Chakraborty via GitGitGadget, Sep 19, 2022
  7. Derrick StoleeSep 19, 2022
  8. Derrick StoleeSep 19, 2022
  9. Junio C HamanoSep 19, 2022
  10. Derrick StoleeSep 20, 2022
  11. Abhradeep ChakrabortySep 20, 2022
  12. Abhradeep ChakrabortySep 20, 2022
  13. Abhradeep ChakrabortySep 20, 2022
  14. Taylor BlauSep 20, 2022
  15. Abhradeep ChakrabortySep 21, 2022
  16. Junio C HamanoSep 21, 2022
  17. Junio C HamanoSep 30, 2022
  18. Abhradeep ChakrabortySep 30, 2022
  19. Abhradeep ChakrabortyOct 30, 2022
  20. Derrick StoleeOct 30, 2022
  21. Abhradeep ChakrabortyOct 31, 2022
  22. Junio C HamanoOct 31, 2022
  23. C99 -> C11 or C17? (was: [PATCH 3/5] roaring: teach Git to write roaring bitmaps)Ævar Arnfjörð Bjarmason, Oct 31, 2022
  24. rsbecker@nexbridge.comOct 31, 2022
  25. Abhradeep ChakrabortyNov 1, 2022

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.