On Sun, Mar 28, 2010 at 12:17:28PM -0400, Jeff King wrote: > If I understand you right, you are proposing a separate program > that you would pass as a fasttextconv helper, and that would look in a > notes tree. So you would still have a per-diff fork/exec, and pipe all > the data. > > I was thinking of actually doing it in-core, so cache hits would be as > lightweight as a notes lookup (and cache misses obviously would still > fork/exec a helper, but we don't care too much since the helper's time > to convert will dominate in that path). Side note: I think I might prototype it as a separate program and see what kind of speed I can get. > > Pruning the cache is done be deleting the refs/notes/bikeshed ref, > > truncating it by truncating it's DAG (filter-branch...). > > Yeah, that would work. It just means it's one more thing the user has to > deal with. I didn't want to have to introduce a "git textconv" > management helper. ;) Other side note: it's not even that it's that hard to prune. It's that you might tweak your config, and then you have to _remember_ to prune. -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