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

Re: What's cooking in git.git (Jan 2009, #05; Wed, 21)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 22, 2009, 05:13 UTC
Message-ID
<alpine.DEB.1.00.0901220606040.3586@pacific.mpi-cbg.de>
In-Reply-To
<7vab9kataf.fsf@gitster.siamese.dyndns.org>
Hi,
On Wed, 21 Jan 2009, Junio C Hamano wrote:
Show 10 quoted lines
> * js/notes (Tue Jan 13 20:57:16 2009 +0100) 6 commits
>  + git-notes: fix printing of multi-line notes
>  + notes: fix core.notesRef documentation
>  + Add an expensive test for git-notes
>  + Speed up git notes lookup
>  + Add a script to edit/inspect notes
>  + Introduce commit notes
> 
> It would be nice to hear a real world success story using the notes
> mechanism before casting this design in stone.

I'd like to have some profiling done before that. For example, I am still a bit unsure how the things would perform with a 50-deep delta chain for a notes tree having 50,000+ notes in it (which I think will not be all that unreasonable for a medium-sized project that stores bug-tracking information in the notes).

I have a gut feeling that the performance dip I saw is a direct result of doing away with the fan-out "subdirectories": remember, originally, I had a tree structure much like the loose objects in .git/objects/??/, while Peff convinced me that a flat tree object should be enough.

I could be wrong on that, though.
> * js/patience-diff (Thu Jan 1 17:39:37 2009 +0100) 3 commits
>  + bash completions: Add the --patience option
>  + Introduce the diff option '--patience'
>  + Implement the patience diff algorithm

There is this one issue that my patience's output differs from bzr's. Since the patience diff algorithm is so lousily documented, I do not know if it is due to my misunderstanding the algorithm, or due to bzr doing something clever in addition.

I'd be thankful if somebody could clarify that issue.

Ciao, Dscho

Previous: Jeff KingNext: Sam Vilain
Message 15 of 23 in “What's cooking in git.git (Jan 2009, #05; Wed, 21)”
  1. Junio C HamanoJan 22, 2009
  2. Jeff KingJan 22, 2009
  3. 1/5 Windows: Fix signal numbersJeff King, Jan 22, 2009
  4. 2/5 diff: refactor tempfile cleanup handlingJeff King, Jan 22, 2009
  5. 3/5 chain kill signals for cleanup functionsJeff King, Jan 22, 2009
  6. Jeff KingJan 30, 2009
  7. Johannes SixtJan 30, 2009
  8. Jeff KingJan 30, 2009
  9. Junio C HamanoJan 31, 2009
  10. Jeff KingJan 31, 2009
  11. Jeff KingJan 31, 2009
  12. Junio C HamanoFeb 1, 2009
  13. 4/5 refactor signal handling for cleanup functionsJeff King, Jan 22, 2009
  14. 5/5 pager: do wait_for_pager on signal deathJeff King, Jan 22, 2009
  15. Johannes SchindelinJan 22, 2009
  16. Sam VilainJan 31, 2009
  17. Jeff KingJan 31, 2009
  18. split notes [was: Re: What's cooking in git.git (Jan 2009, #05; Wed, 21)]Sam Vilain, Feb 1, 2009
  19. split notes [was: Re: What's cooking in git.git (Jan 2009, #05; Wed, 21)]Sam Vilain, Feb 1, 2009
  20. Jakub NarebskiFeb 1, 2009
  21. Boyd Stephen Smith Jr.Jan 22, 2009
  22. Junio C HamanoJan 23, 2009
  23. Boyd Stephen Smith Jr.Jan 27, 2009

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.