Steven Grimm <koreth@xxxxxxxxxxxxx> writes: > David Kastrup wrote: >> You'll potentially get accumulating unfinished files from >> aborted/killed repack processes. > > Which can get cleaned up when the next repack starts. This is no > different from unfinished files accumulating from aborted/killed > manual repacks. > >> If communication fails, you'll get a >> new repack session for every command you start. > > Git handles this already: > > $ git-gc > fatal: unable to create '.git/packed-refs.lock': File exists > error: failed to run pack-refs > > Presumably in that case you would simply not fire up a new repack. > >> If a repository is used by multiple people... >> > > Then the first one will kick off the repack, and subsequent ones won't. And the first one might get habitually killed by the user unwittingly having started it (because he really only logs in for shorter amounts of times than needed for git-gc to finish), wasting disk space and time all the while. -- David Kastrup - 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
