Nicolas Pitre <nico@xxxxxxx> writes:
>> Can we also have "why this is a good idea", "what problem this solves"?
>
> FWIW, my agreeing with the "why this is a good idea" can be translated
> into:
>
> Acked-by: Nicolas Pitre <nico@xxxxxxx>
Hmmm. Is it _that_ obvious?
At least it would be easier to readers if we had something like this in
the documentation (and/or the commit message):
"git gc" used to never prune unreachable objects without being
explicitly told to, with its --prune option. This left cruft to
accumulate; the user eventually has to run "git prune" manually.
It is safe to prune old objects that are unreachable from refs nor
reflogs. "git gc" is updated to run "git prune --expire 2.weeks.ago"
so that users has to run "git prune" by hand much less often.
Is it too much to ask for regulars to set the example of justifying why
each of the change is a good idea?
--
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
