Re: is git-unpack-objects now redundant for 'git-push' and friends?

[Junio C Hamano <junkio@cox.net>]

Sam Vilain <sam@vilain.net> writes:

> When pushing or pulling to/from a repository, why unpack the objects?
> Why not just fsck and then throw the pack into $GIT_DIR/objects/pack?
>...
> I suspect that this was never changed, because there never used to be
> more than one packfile allowed, correct?

We've supported more than one packs at the same time from the
day we supported packs.

Primary reason that push never keeps the pack is that explosion
into loose objects hurts you only at the first round and later
pushes are supposed to be much smaller, so changing it to keep
the pack for the initial one has a very small value making it a
very low priority change.  Not keeping the pack on push makes it
possible to always use --thin for pushing if we wanted to.

On the fetch side you could use --keep option when you know the
fetch will be huge.