Taylor Blau <me@xxxxxxxxxxxx> writes: > The thing I think Jonathan seeks to prevent is older versions of Git > gc'ing a repo that has cruft packs. I think I may need you to clarify a > little, sorry :-(. By making controlled rollout of the use of "--cruft" option (and the assumption here is that a large organization setting people do not manually say "gc --cruft", and they can ship their maintenance scripts that may be run via cron or whatever with and without "--cruft"), you can control the number of repositories that can potentially see older versions of Git running gc on with cruft packs. Those users, for whom it is not their turn to start using "--cruft" enabled version of the script, will not have cruft packs, so it does not matter if they keep an older version of Git somewhere hidden in a hermetic build of an IDE that bundles Git and gc kicks in for them.
