This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Run git prune on sourceware.org?
- From: Zack Weinberg <zackw at panix dot com>
- To: libc-alpha at sourceware dot org
- Date: Fri, 1 Sep 2017 09:42:39 -0400
- Subject: Re: Run git prune on sourceware.org?
- Authentication-results: sourceware.org; auth=none
- References: <e71ea305-8fd3-e320-ac66-ec04a2339f84@redhat.com> <mvm7exjhoq3.fsf@suse.de>
On 08/31/2017 09:05 AM, Andreas Schwab wrote:
> On Aug 31 2017, Florian Weimer <fweimer@redhat.com> wrote:
>
>> Git started complaining during pushes:
>>
>> Auto packing the repository for optimum performance.
>> warning: There are too many unreachable loose objects; run 'git prune'
>> to remove them.
>>
>> And indeed:
>>
>> $ git prune -n | cut -d\ -f 2 | sort | uniq -c
>> 51 blob
>> 313 commit
>> 719 tree
>>
>> So it seems that there is quite some room for cleanup.
>>
>> Do you think this is safe to run?
>
> They should be pruned automatically after some grace period (two weeks
> by default) by the next git gc --auto.
Does that ever actually happen *to the sourceware.org repository*? I am
getting the same complaints, but `git prune -n` reports nothing to do to
my local clone.
zw