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

Re: Confusing text in git-prune.txt

From
Adeodato Simó <dato@net.com.org.es>
Date
Jan 16, 2009, 17:02 UTC
Message-ID
<20090116170217.GA14855@chistera.yi.org>
In-Reply-To
<4970BC25.7020007@viscovery.net>
* Johannes Sixt [Fri, 16 Jan 2009 17:56:05 +0100]:
> Adeodato Simó schrieb:
> > From git-prune.txt:
Show 5 quoted lines
> >     [...] prunes all unpacked objects unreachable from any of
> >     these head objects from the object database. In addition,
> >     it prunes the unpacked objects that are also found in packs by
> >     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >     running git-prune-packed.
> > How can "unpacked objects" be "found in packs"?
> An object can exist more than once in the database. prune-packed removes
> the loose (unpacked) instance of the object if it also available in a pack.
Ah, thanks, that explains everything.

I read the manpage for git-prune-unpacked, but I didn't manage to figure it out. It may have helped if instead of saying:

    git-prune-packed - Remove extra objects that are already in pack files
it would have said:
    git-prune-packed - Remove loose objects that are already in pack files
                              ^^^^^

By stating that those objects are "extra", we're losing the information of where are they. And by reading that synopsis, one can already infer they are "extra".

Cheers,
-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
                                 Listening to: Radiohead - Bodysnatchers
Previous: Johannes Sixt
Message 3 of 3 in “Confusing text in git-prune.txt”
  1. Adeodato SimóJan 16, 2009
  2. Johannes SixtJan 16, 2009
  3. Adeodato SimóJan 16, 2009

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.