Re: [PATCHv1+eps] git-repack.txt: Clarify implications of -a for dumb protocols

From: Stephen Boyd <bebarino@gmail.com>
Date: Jun 5, 2009, 19:14 UTC
Message-ID: <780e0a6b0906051214t76f2bf37u96cc0b8039f63d23@mail.gmail.com>
In-Reply-To: <4A28D470.5030403@drmicha.warpmail.net>

On Fri, Jun 5, 2009 at 1:16 AM, Michael J Gruber<git@drmicha.warpmail.net> wrote:

Show 13 quoted lines

> Stephen Boyd venit, vidit, dixit 04.06.2009 21:46:
>> Instead of adding this, why don't we just remove the part about dumb
>> protocols? So just say that it's especially useful for private
>> development. Then, if we really want to keep this performance note
>> just add it after the paragraph in one of those "+" things (What are
>> those called?)
>
> ...because "repack -a" hurts *badly* on even midsized repos when dumb
> protocols are used. On the other hand, using it isn't that much of an
> improvement in terms of pack size, unless you repack manually very often
> and, thus, produce many small packs. So, "gc --auto" users should be
> fine in any case (dumb or not - the protocol, that is...) as long as
> they don't use "-a".

Maybe I spoke wrongly. I'm suggesting something like

       Especially useful when packing a repository that is used
       for private development.  Use with '-d'.  This will clean up
       the objects that `git prune` leaves behind, but
       `git fsck --full` shows as dangling.
+
Note: Users fetching over dumb protocols will have to fetch the
whole pack in order to get any contained object, no matter how
many other objects in that pack they already have locally.

I think this Note part probably needs some work though.