Re: People unaware of the importance of "git gc"?

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Sep 5, 2007, 17:31 UTC
Message-ID: <vpq1wddkohr.fsf@bauges.imag.fr>
In-Reply-To: <D32A7C27-EAF5-4156-BE0E-99FE3D948AE8@wgaf.org>

Johan De Messemaeker <johan.demessemaeker@wgaf.org> writes:

Show 10 quoted lines

>> Currently, AFAIK, that can only be done with a (trivial) script
>> external to git. I suppose this can easily be added to the core git
>> porcelain. Perhaps a "git gc --recursive" would do.
>>
>> It doesn't solve the problem, but makes it easier to solve it (git gc
>> --recursive in cron for example).
>
> I'm a git newb so I can be wrong here but ...
>
> Why --recursive? Why not use the submodule-information ?

all projects are not necessarily subprojects of each others.

I have ~/teaching/some-course/.git (well, almost) and ~/etc/.git which are two unrelated projects, and to "git gc" both of them, I need either a script, or two manual invocations.

(yes, I'm really talking about something trivial)

-- 
Matthieu