On Thu, Dec 08, 2022 at 02:16:31AM +0100, Michal Suchánek wrote: > > A "git gc" on a "live" repo is always racy in theory, but the odds that > > you'll run into data corrupting trouble tends to approach zero as you > > increase the gc.pruneExpire setting, with the default 2 weeks being more > > than enough for even the most paranoid user. > > And that two weeks expiration applies to what, exactly? > > For commits there is author date and commit date but many other objecs > won't have these I suppose. And the date when the object is pushed into > the repository is unrelated to these two, anyway. In this case it's the mtime on the object file (or the pack containing it). But yes, it is far from a complete race-free solution. -Peff
