E R wrote: > Btw - what kind of risks are involved in using git when test > t5304-prune.sh doesn't pass? Do we risk repository corruption? For the case in the test, git-prune is failing to remove an object that it should, which won't cause repo corruption. It will just cause retention of an object for longer than it is needed. I suspect this is caused by some flaw in the NFS client (disclosure: IANAKH). In practice, I don't think you'll experience this flaw. I think it shows up in the test because we are manually adjusting the mtime of the objects and then immediately trying to prune them and this must tweak whatever code has a bug. I have been using git on 5.2 for a couple of months now with no problem. Admittedly, prune is a rare operation, usually triggered by git-gc. -brandon -- 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
