"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > +The optional configuration variable 'gc.reflogExpireUnreachable' > +can be set to indicate how long historical reflog entries which > +are not part of the current branch should remain available in > +this repository. These types of entries are generally created as > +a result of using `git commit \--amend` or `git rebase` and are the > +commits prior to the amend or rebase occuring. Since these changes > +are not part of the current project most users will want to expire > +them sooner. This option defaults to '60 days'. Should I update the default expire-unreachable in builtin-reflog to match 60 days? - 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