Jeff King wrote: > On Sun, Dec 14, 2008 at 12:17:07PM +0100, Johannes Schindelin wrote: > >>> Which annoyingly has no discussion about _why_ it no longer has an >>> effect. But I suspect it has something to do with 25ee973 (gc: call >>> "prune --expire 2.weeks.ago" by default, 2008-03-12) by you. >> Oops. >> >> But I thought that git gc --prune does expire _all_ dangling loose >> objects _now_, not with --expire 2.weeks.ago. > > Nope, see 25ee973. You explicitly wrote: > > Note that this new behaviour makes "--prune" be a no-op. > > That being said, I think that is perhaps a reasonable thing for --prune > to do (and I don't think there is any conflict with the name, because > that is what it _used_ to do before becoming a no-op). But nobody has > actually implemented it. Maybe --mrproper would be a more appropriate name. -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
