On Mon, 2009-09-07 at 16:11 +0200, Nick Edelen wrote: > This last patch ^^ You don't need to write comments like "This patch"; in the history such words are meaningless. > provides a working integration of rev-cache into the revision > walker, along with some touch-ups: > - integration into revision walker and list-objects > - tweak of object generation "tweak" ? > - more fluid handling of damaged cache slices What does this mean? > - numerous tests for both features from the previous patch, and the > integration's integrity > 'Integration' is rather broad -- a more detailed description follows for each > aspect: > - rev-cache > the traversal mechanism is updated to handle many of the non-prune options > rev-list does (date limiting, slop-handling, etc.), and is adjusted to allow > for non-fatal cache-traversal failures. > > - revision walker > both limited and unlimited traversal attempt to use the cache when possible, > smoothly falling back if it's not. > > - list-objects > object listing does not recurse into cached trees, and has been adjusted to > guarantee commit-tag-tree-blob ordering. This is quite a long commit message. Is the above detail all useful? Can it be split into one patch for each of the above integrations? > Signed-off-by: Nick Edelen <sirnot@xxxxxxxxx> Sam -- 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