From: Junio C Hamano Date: Sun, 15 Jul 2007 23:36:50 GMT Subject: Re: [PATCH 2/6] Introduce commit notes Message-ID: <7vlkdhck8d.fsf@assigned-by-dhcp.cox.net> In-Reply-To: Johannes Schindelin 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. 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 ;-)