git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adeodato Simó" <dato@net.com.org.es>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: Confusing text in git-prune.txt
Date: Fri, 16 Jan 2009 18:02:17 +0100	[thread overview]
Message-ID: <20090116170217.GA14855@chistera.yi.org> (raw)
In-Reply-To: <4970BC25.7020007@viscovery.net>

* Johannes Sixt [Fri, 16 Jan 2009 17:56:05 +0100]:

> Adeodato Simó schrieb:
> > From git-prune.txt:

> >     [...] 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

      reply	other threads:[~2009-01-16 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 16:50 Confusing text in git-prune.txt Adeodato Simó
2009-01-16 16:56 ` Johannes Sixt
2009-01-16 17:02   ` Adeodato Simó [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090116170217.GA14855@chistera.yi.org \
    --to=dato@net.com.org.es \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).