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? -- 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