Re: What's cooking in git.git (Mar 2010, #03; Wed, 10)
- From
Johan Herland <johan@herland.net>
- Date
- Mar 11, 2010, 11:09 UTC
- Message-ID
- <201003111209.10445.johan@herland.net>
- In-Reply-To
- <7v7hpj4k7w.fsf@alter.siamese.dyndns.org>
On Thursday 11 March 2010, Junio C Hamano wrote:
Show 5 quoted lines
> [Cooking] > > * sb/notes-parse-opt (2010-02-27) 1 commit > - notes: rework subcommands and parse options > (this branch uses early parts of jh/notes and tr/notes-display.)
The latest iteration of this looked good to me, but it might need a re-roll once tr/notes-display is set in stone/'next'.
Show 18 quoted lines
> * tr/notes-display (2010-03-10) 13 commits > - git-notes(1): add a section about the meaning of history > - notes: track whether notes_trees were changed at all > - notes: add shorthand --ref to override GIT_NOTES_REF > - commit --amend: copy notes to the new commit > - rebase: support automatic notes copying > - notes: implement helpers needed for note copying during rewrite > - notes: implement 'git notes copy --stdin' > - rebase -i: invoke post-rewrite hook > - rebase: invoke post-rewrite hook > - commit --amend: invoke post-rewrite hook > - Documentation: document post-rewrite hook > - Support showing notes from more than one notes tree > - test-lib: unset GIT_NOTES_REF to stop it from influencing tests > (this branch uses early parts of jh/notes; is used by > sb/notes-parse-opt.) > > Re-rolled. I think this is ready for 'next'. Comments?
I just reviewed it, and it looks good to me.
...Johan
-- Johan Herland, <johan@herland.net> www.herland.net