git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Sep 2021, #08; Mon, 27)

From
NSNeeraj Singh <nksingh85@gmail.com>
Date
Sep 28, 2021, 21:00 UTC
Message-ID
<20210928210059.vy5isvmcj75vufdu@neerajsi-x1.localdomain>
In-Reply-To
<xmqqilykliiz.fsf@gitster.g>
On Tue, Sep 28, 2021 at 10:25:08AM -0700, Junio C Hamano wrote:
Show 23 quoted lines
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> 
> > I haven't poked at it much, but haven't you and Neeraj Singh (CC'd)
> > independently come up with two slightly different changes in
> > tmp-objdir.c to do the same thing? See the tmp-objdir.c part of:
> >
> > http://lore.kernel.org/git/543ea3569342165363c1602ce36683a54dce7a0b.1632527609.git.gitgitgadget@gmail.com
> >
> > And your:
> >
> > http://lore.kernel.org/git/67d3b2b09f9ddda616cdd0d1b12ab7afc73670ed.1630376800.git.gitgitgadget@gmail.com
> >
> > I.e. yours has the object database managed outside, his has it added to
> > "struct tmp_objdir", but it's the same objdir dance isn't it?
> 
> They touch the same tmp-objdir, but unlike the original use in the
> receive-pack (i.e. responding to "git push") with the intention to
> add the objects collected in them back to the primary, remerge-diff
> wants to discard what was added there at the end.  I do not think it
> would directly help the bulk-fsync stuff (but I didn't quite see why
> bulk-fsync stuff needed to _add_ new functions to tmp-objdir API,
> instead of just being a customer of tmp-objdir API), where it wants
> to do the same _migrate() dance in the end.

Both Elijah and I needed the same functionality of having a writable ODB in the current process, which wasn't previously provided by tmp-objdir.

I'm making a new patch which is an amalgamation of Elijah's version and mine. I'll rebase and resend my patch series with that version and I'll also make a modified version of Elijah's branch available on github.

Thanks, Neeraj

Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 40 in “What's cooking in git.git (Sep 2021, #08; Mon, 27)”
  1. Junio C HamanoSep 28, 2021
  2. Ævar Arnfjörð BjarmasonSep 28, 2021
  3. Junio C HamanoSep 28, 2021
  4. Elijah NewrenSep 28, 2021
  5. Ævar Arnfjörð BjarmasonSep 28, 2021
  6. Junio C HamanoSep 28, 2021
  7. Neeraj SinghSep 28, 2021
  8. Junio C HamanoSep 28, 2021
  9. Neeraj SinghSep 28, 2021
  10. Junio C HamanoOct 7, 2021
  11. Elijah NewrenOct 8, 2021
  12. Neeraj SinghOct 8, 2021
  13. Junio C HamanoOct 8, 2021
  14. Ævar Arnfjörð BjarmasonSep 28, 2021
  15. Junio C HamanoSep 28, 2021
  16. Derrick StoleeSep 28, 2021
  17. Junio C HamanoSep 28, 2021
  18. Derrick StoleeSep 28, 2021
  19. Junio C HamanoSep 28, 2021
  20. Elijah NewrenSep 29, 2021
  21. Jeff KingSep 28, 2021
  22. Jeff KingSep 28, 2021
  23. Neeraj SinghSep 29, 2021
  24. Jeff KingSep 30, 2021
  25. Elijah NewrenOct 1, 2021
  26. Junio C HamanoOct 1, 2021
  27. Neeraj SinghOct 1, 2021
  28. Elijah NewrenOct 1, 2021
  29. Elijah NewrenOct 1, 2021
  30. Junio C HamanoOct 1, 2021
  31. Elijah NewrenOct 1, 2021
  32. Elijah NewrenOct 4, 2021
  33. da/difftool (was: Re: What's cooking in git.git (Sep 2021, #08; Mon, 27))Ævar Arnfjörð Bjarmason, Sep 28, 2021
  34. ns/batched-fsync & en/remerge-diff (was Re: What's cooking in git.git (Sep 2021, #08; Mon, 27))Ævar Arnfjörð Bjarmason, Sep 28, 2021
  35. sg/test-split-index-fix (was Re: What's cooking in git.git (Sep 2021, #08; Mon, 27))Ævar Arnfjörð Bjarmason, Sep 28, 2021
  36. hn/reftable (Re: What's cooking in git.git (Sep 2021, #08; Mon, 27))Ævar Arnfjörð Bjarmason, Sep 28, 2021
  37. Han-Wen NienhuysSep 28, 2021
  38. Carlo ArenasSep 30, 2021
  39. Fabian StelzerSep 29, 2021
  40. Junio C HamanoSep 30, 2021

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.