Re: [PATCHv5 00/14] git notes
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Sep 8, 2009, 21:39 UTC
- Message-ID
- <20090908213944.GX1033@spearce.org>
- In-Reply-To
- <fabb9a1e0909081436x72c71b0bv51d8f198cd82f289@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> wrote:
Show 10 quoted lines
> On Tue, Sep 8, 2009 at 23:10, Shawn O. Pearce<spearce@spearce.org> wrote: > > So most commits (66%) would have only 1 version (and 1 note) > > related to them in the note tree, but if I use the same note tree > > for final commits as individual revisions considered, at least 18% > > of the commits in the final history of the project would actually > > have two notes, and 7.5% would have 3 notes. > > You could however store all that information in one note, yes? Since > the 'latest version' is the one committed, you can include the notes > for all the previous ones at commit time?
Uh, but the natural way to index those is by commit, and each different revision of a change is a different commit. Why delete the prior revision information and move it to the final commit note? Someone who has the prior revisions in their reflog and is doing `git log -g --notes` might want to see that annotation.
-- Shawn.