git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <junkio@cox.net>
Date
Oct 10, 2006, 17:44 UTC
Message-ID
<7v7iz82hh4.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<452B9EE8.5020702@vilain.net>
Sam Vilain <sam@vilain.net> writes:
Show 5 quoted lines
> 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.

Previous: Shawn Pearce
Message 3 of 3 in “is git-unpack-objects now redundant for 'git-push' and friends?”
  1. Sam VilainOct 10, 2006
  2. Shawn PearceOct 10, 2006
  3. Junio C HamanoOct 10, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.