Hi, On Sun, 10 Feb 2008, Jon Smirl wrote: > In the lazy clone thread there is mention of a large, generated file > being checked into the tree. Let's say we have a tree like this and it > is ok to delete the generated file since it didn't really need to be > checked in. Is there a procedure to chase down all the revisions, delete > them, and then regenerate the commits to reflect the deletion? I don't > need this tool, I'm just wondering if there is a reasonable solution to > the problem. filter-branch. Ciao, Dscho - 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