Re: `git prune` doc or implementation defect, or user misunderstanding

On Wed, May 8, 2013 at 10:41 AM, Johannes Sixt wrote: > git gc moves unreachable objects that were packed before to the loose > object store, from where they can be pruned. Thanks. That was the piece I was missing. I assumed `git gc` did the opposite. -- Matt McClure http://matthewlmcclure.com

Re: `git prune` doc or implementation defect, or user misunderstanding

Am 5/8/2013 16:19, schrieb Matt McClure: > My interpretation of that is that `git prune` will not prune packed objects > by default. The following behavior seems inconsistent with that > interpretation. > > [git@438587-beefcake01 panama.git]$ git prune -n | wc -l > 9210 You have 9210 unreachable,

`git prune` doc or implementation defect, or user misunderstanding

The `git prune` documentation says: This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command line, and prunes all unpacked objects unreachable from any of these head objects from th