Am 1/28/2011 15:37, schrieb Shawn Pearce: > A simple fix is to use --heads --tags by default like I do here, but > make the actual parameters we feed to rev-list configurable. A > repository owner could select only the master branch as input to > rev-list, making it less likely the topic branches would be > considered. Unfortunately that requires direct access to the > repository. It fails for a site like GitHub, where you don't manage > the repository at all. Let's define a ref hierarchy, refs/cache-pack, that names the cache pack tips. A cache pack would be generated for each ref found in that hierarchy. Then these commits are under user control even on github, because you can just push the refs. Junio would perhaps choose a release tag, and corresponding commits in the man and html histories. The choice would not be completely automatic, though. -- Hannes -- 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