Johannes Schindelin wrote: > If you want to override this grace period, just set the config variable > gc.pruneExpire to a different value; an example would be > > [gc] > pruneExpire = 6.months.ago > > if you feel really paranoid. > > Note that this new behaviour does not affect git-gc when you pass the > option --prune; in that case, prune will clean up the loose objects with no > grace period at all. Hmm. Perhaps 'git-gc' should always call 'prune' with the '--expire' argument for simplicity of the 'git-gc' interface and --prune should become a noop? Is 'git-gc --prune' still useful to end users when those in-the-know can use git-prune when they really want all loose unreferenced objects to be removed? Also, what about clones created with --shared or --reference? Should there be a way to disable this functionality? gc.pruneExpire never -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
