From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2010, #06; Wed, 20)
Date: Thu, 21 Jan 2010 02:06:23 +0100 [thread overview]
Message-ID: <fabb9a1e1001201706i4c7ffaecs55153c9220bc5992@mail.gmail.com> (raw)
In-Reply-To: <7vljfsxos5.fsf@alter.siamese.dyndns.org>
Heya,
On Thu, Jan 21, 2010 at 01:52, Junio C Hamano <gitster@pobox.com> wrote:
> * jh/notes (2010-01-17) 23 commits
> - builtin-gc: Teach the new --notes option to garbage-collect notes
> - Notes API: gc_notes(): Prune notes that belong to non-existing objects
> - t3305: Verify that removing notes triggers automatic fanout consolidation
> - builtin-notes: Teach -d option for deleting existing notes
> - Teach builtin-notes to remove empty notes
> - Teach notes code to properly preserve non-notes in the notes tree
> - t3305: Verify that adding many notes with git-notes triggers increased fanout
> - t3301: Verify successful annotation of non-commits
> - Builtin-ify git-notes
> - Refactor notes concatenation into a flexible interface for combining notes
> - Notes API: Allow multiple concurrent notes trees with new struct notes_tree
> - Notes API: write_notes_tree(): Store the notes tree in the database
> - 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: remove_note(): Remove note objects from the notes tree structure
> - 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
> - Add tests for checking correct handling of $GIT_NOTES_REF and core.notesRef
> - Notes API: get_commit_notes() -> format_note() + remove the commit restriction
> - Minor non-functional fixes to notes.c
> (merged to 'next' on 2010-01-02 at ae42130)
> + Add more testcases to test fast-import of notes
> + Rename t9301 to t9350, to make room for more fast-import tests
> + fast-import: Proper notes tree manipulation
>
> Updated with a re-roll.
Just checking, you reverted all from next (with exception of the first
three), and now re-queued it to pu, with the first three still in
next? Or did I mis-remember and did only the first three make it to
next in the first place?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-01-21 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 0:52 What's cooking in git.git (Jan 2010, #06; Wed, 20) Junio C Hamano
2010-01-21 1:06 ` Sverre Rabbelier [this message]
2010-01-21 1:40 ` Johan Herland
2010-01-21 2:04 ` Sverre Rabbelier
2010-01-21 4:06 ` Junio C Hamano
2010-01-21 9:18 ` Johan Herland
2010-01-21 17: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=fabb9a1e1001201706i4c7ffaecs55153c9220bc5992@mail.gmail.com \
--to=srabbelier@gmail.com \
--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).