From: Johan Herland <johan@herland.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2010, #03; Wed, 10)
Date: Thu, 11 Mar 2010 12:09:10 +0100 [thread overview]
Message-ID: <201003111209.10445.johan@herland.net> (raw)
In-Reply-To: <7v7hpj4k7w.fsf@alter.siamese.dyndns.org>
On Thursday 11 March 2010, Junio C Hamano wrote:
> [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'.
> * 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
next prev parent reply other threads:[~2010-03-11 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 3:21 What's cooking in git.git (Mar 2010, #03; Wed, 10) Junio C Hamano
2010-03-11 11:09 ` Johan Herland [this message]
2010-03-11 12:13 ` Junio C Hamano
2010-03-12 16:40 ` Thomas Rast
2010-03-12 4:41 ` Nguyen Thai Ngoc Duy
2010-03-12 5:40 ` Junio C Hamano
2010-03-12 5:52 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003111209.10445.johan@herland.net \
--to=johan@herland.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).