Re: What's cooking in git.git (Oct 2009, #03; Mon, 19)

[Johan Herland <johan@herland.net>]

On Monday 19 October 2009, Junio C Hamano wrote:
> * jh/notes (2009-10-09) 22 commits.
>  - fast-import: Proper notes tree manipulation using the notes API
>  - Refactor notes concatenation into a flexible interface for combining notes
>  - Notes API: Allow multiple concurrent notes trees with new struct notes_tree
>  - Notes API: for_each_note(): Traverse the entire notes tree with a callback
>  - Notes API: get_note(): Return the note annotating the given object
>  - Notes API: add_note(): Add note objects to the internal notes tree structure
>  - Notes API: init_notes(): Initialize the notes tree from the given notes ref
>  - Notes API: get_commit_notes() -> format_note() + remove the commit restriction
>  - Add selftests verifying concatenation of multiple notes for the same commit
>  - Refactor notes code to concatenate multiple notes annotating the same object
>  - Add selftests verifying that we can parse notes trees with various fanouts
>  - Teach the notes lookup code to parse notes trees with various fanout schemes
>  - Teach notes code to free its internal data structures on request
>  - Add '%N'-format for pretty-printing commit notes
>  - Add flags to get_commit_notes() to control the format of the note string
>  - t3302-notes-index-expensive: Speed up create_repo()
>  - fast-import: Add support for importing commit notes
>  - Teach "-m <msg>" and "-F <file>" to "git notes edit"
>  - Add an expensive test for git-notes
>  - Speed up git notes lookup
>  - Add a script to edit/inspect notes
>  - Introduce commit notes
>  (this branch uses sr/gfi-options.)

Nope. This branch does not use sr/gfi-options. The jh/cvs-helper branch
does, though.

> Is this good for 'next' now?

Not all of it.

I suspect the first 14 patches are stable and 'next'-worthy, although
it would be nice if Dscho had the time to ACK them.

The last patch (#22) needs some major rework based on Shawn's comments
(I'm working on that, although I currently have less time than I hoped
for), and that rework might ripple into patches #15 through #21.


...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net