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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sam Vilain <sam@xxxxxxxxxx> 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.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]