git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: walt <wa1ter@myrealbox.com>
Cc: git@vger.kernel.org
Subject: Re: Question about git-prune
Date: Sat, 30 Jun 2007 13:12:39 -0700	[thread overview]
Message-ID: <7vps3db3rc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <f66d3l$sa6$1@sea.gmane.org> (wa1ter@myrealbox.com's message of "Sat, 30 Jun 2007 13:06:09 -0700")

walt <wa1ter@myrealbox.com> writes:

>> Probably the objects were packed.
>
> I also tried git-prune-packed, which also did nothing AFAICT.

Of course it wouldn't; prune-packed is to prune loose objects
that also appear in packs.

What is happening is:

 - You create a pack that has everything reachable from refs at
   one point;

 - You pull or do your own development; the set of objects
   reachable from refs change from the above set.  This set is
   superset of the above only if there is no rewind is
   involved.  Otherwise, some objects already packed in the
   previous step are now unreachable.

 - git-prune and git-prune-packed are about removing loose
   objects.  They never go into existing packs and eradicate
   objects from them.

When you have unreachable cruft in packs, repacking is the only
way to rid them ("git repack -a -d", which is run by "git gc").

  reply	other threads:[~2007-06-30 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 16:29 Question about git-prune walt
2007-06-30 18:02 ` Johannes Schindelin
2007-06-30 20:06   ` walt
2007-06-30 20:12     ` Junio C Hamano [this message]
2007-06-30 20:18     ` Johannes Schindelin

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=7vps3db3rc.fsf@assigned-by-dhcp.cox.net \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=wa1ter@myrealbox.com \
    /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).