Re: [PATCH 00/15] git-note: A mechanisim for providing free-form after-the-fact annotations on commits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 28 May 2007, Linus Torvalds wrote:
> 
> On Mon, 28 May 2007, Johan Herland wrote:
> > 
> > I still don't see what makes note objects inherently more expensive than
> > commit objects. Except for the refs, of course, but we're getting rid
> > of those (at least replacing them with a more efficient reverse mapping).
> 
> It's exactly the refs that I worry about.
> 
> Anything that needs to read in all notes at startup is going to be _slow_.
> 
> In contrast, commits we read when (and only when) we need them.

Ok. But the reverse mapping will help with this, won't it?
We'll look up the interesting commits and find their associated
note objects directly.

BTW, if you use "git-note -l <commit>" it'll go directly to <commit>'s
subdir in refs/notes and never look at any other notes.

Of course, this currently does not help the plumbing much, which uses
for_each_note_ref() instead...


...Johan

-- 
Johan Herland, <johan@xxxxxxxxxxx>
www.herland.net
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux