Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > On Sat, 13 Dec 2008, Markus Heidelberg wrote: > > > - __gitcomp "--prune --aggressive" > > + __gitcomp "--aggressive" > > git gc --prune is deprecated? That's news to me. More like "git gc --prune" is no-op now. > How would you suggest, then, to remove the loose objects you always get > with conflicts in a merge? "git gc" does pruning of loose objects, but protected by grace period for loose objects with gc.pruneexpire You always have (admittedly lowe level) git-prune. -- Jakub Narebski Poland ShadeHawk on #git -- 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
