Re: dangling commits
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jan 16, 2006, 09:27 UTC
- Message-ID
- <7vr778wmj3.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <20060116085238.GA3768@fiberbit.xs4all.nl>
Marco Roeland <marco.roeland@xs4all.nl> writes:
> As far as I know although packs are used in transferring the commits to > your local repository they are stored there as separate objects,...
That is true only when you are using git native protocols (i.e. git:// and git over ssh). Some people pull over dumb transport (http -- some others still use rsync which is even dumber and has serious limitations), and when you need objects that are contained in a pack at the upstream, the packfile is downloaded as a whole, and it is left packed on your end.
Even when you use git native protocol, the objects the initial clone gives you are kept packed, so when I rewind and rebuild "pu" to make some of these objects orphaned, they will stay in the pack the initial clone gave you. Unpack+repack is needed to get rid of them.
As you said, they should not hurt much in practice, though.