On Sun, Feb 07, 2010 at 10:48:58AM -0800, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > ... I think you would do better > > to simply store a tree sha1 inside the note blob, and callers who were > > interested in the tree contents could then dereference it and examine as > > they saw fit. The only caveat is that you need some way of telling git > > that the referenced trees are reachable and not to be pruned. > > Thanks for a good summary. To paraphrase the idea, for the "pre-built > binaries" use case, I could update the dodoc.sh script (in 'todo'---that > is what autobuilds the html and man documentation and updates the > corresponding branches at k.org when I push things out to the master > branch) to add a note to the commit from 'master' the docs are generated > from, and the note would say which commits on html and man branches > correspond to that commit. That way, the referenced "trees" are of course > protected because they are reachable from html/man refs. > > Right? Yeah, I think that would work fine. I guess there are cases, though, where somebody might not be keeping a linear history of noted trees in a separate ref (the way you keep html/man refs). In which case they would have to deal with the reachability problem separately. I can't think of an example off the top of my head, though. -Peff -- 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