Hi, On Sun, 15 Jul 2007, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > The notes ref is a branch which contains trees much like the > > loose object trees in .git/objects/. In other words, to get > > at the commit notes for a given SHA-1, take the first two > > hex characters as directory name, and the remaining 38 hex > > characters as base name, and look that up in the notes ref. > > ... > > However, a remedy is near: in a later commit, a .git/notes-index > > will be introduced, a cached mapping from commits to commit notes, > > to be written when the tree name of the notes ref changes. In > > case that notes-index cannot be written, the current (possibly > > slow) code will come into effect again. > > I wonder if it is worth using the fan-out tree structure for the > underlying "note" trees, as the notes-index would be the primary > way to access them. The fan-out tree is a nice fallback solution when you cannot write the notes-index. > Not that I've looked at the code too deeply with an intention of > possibly including it early. I was hoping to see fixes to d/f code in > merge-recursive from either you or Alex instead ;-) Well, yeah. I was kind of trying to cool off from my unpleasant unpack_trees() experience. But I'll look into the issue again this week. Promise. Ciao, Dscho - 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
