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

undocumented git pack-objects --unpacked=file

From
KNKalle Olavi Niemitalo <kon@iki.fi>
Date
Apr 2, 2008, 06:35 UTC
Message-ID
<873aq4sr0l.fsf@Astalo.kon.iki.fi>
A child process of "git repack -a -d -f" was doing:
  PID TTY      STAT   TIME COMMAND
20178 pts/3    R+   491:31 git pack-objects --non-empty --all --reflog --unpacked=pack-41dbbd4c9b63110b8122f9d78a15668aa6b2b273.pack
The git-pack-objects(1) manual page describes:
| git-pack-objects [-q] [--no-reuse-delta] [--delta-base-offset] [--non-empty]
|         [--local] [--incremental] [--window=N] [--depth=N] [--all-progress]
|         [--revs [--unpacked | --all]*] [--stdout | base-name] < object-list
...
| --unpacked
|         This implies --revs. When processing the list of revision
|         arguments read from the standard input, limit the objects
|         packed to those that are not already packed.

However, it does not say what --unpacked=pack-41dbbd4c9b63110b8122f9d78a15668aa6b2b273.pack might mean. grep unpacked= Documentation/* did not find anything either. Could you please document the meaning of this option?

Message 1 of 1 in “undocumented git pack-objects --unpacked=file”
  1. Kalle Olavi NiemitaloApr 2, 2008

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.