git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Wolfgang Denk <wd@denx.de>
Cc: git@vger.kernel.org
Subject: Re: dangling commits
Date: Sun, 15 Jan 2006 14:55:39 -0800	[thread overview]
Message-ID: <7v8xth14pg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060115221108.3ED2E352659@atlas.denx.de> (Wolfgang Denk's message of "Sun, 15 Jan 2006 23:11:08 +0100")

Wolfgang Denk <wd@denx.de> writes:

> Is ther eany way to clean up such a situation and really get  rid  of
> the  dangling  commits?  I understand that I'd first need some way to
> "unpack" the packs, but how to do this? 

The easiest is to repack into a single big ball of wax:

	$ git repack -a -d

If you know the pack the stale object is in, you can move it out
of objects/pack/ and repack only that one.

	$ mv .git/objects/packs/pack-$badone.{idx,pack} .
	$ git unpack-objects <pack-$badone.pack
        $ git repack

After you are done:

	$ git prune

  reply	other threads:[~2006-01-15 22:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 21:05 dangling commits Nick Williams
2006-01-15 20:56 ` Andreas Ericsson
2006-01-15 21:37   ` Nick Williams
2006-01-15 21:15     ` Junio C Hamano
2006-01-15 22:11       ` Wolfgang Denk
2006-01-15 22:55         ` Junio C Hamano [this message]
2006-01-16  8:52         ` Marco Roeland
2006-01-16  9:27           ` Junio C Hamano
2006-01-16 10:17             ` Marco Roeland
2006-01-16 10:28               ` Andreas Ericsson
2006-01-16 11:33                 ` Marco Roeland
2006-01-16 12:05                   ` Andreas Ericsson
2006-01-16 12:40                     ` Marco Roeland
2006-01-16  9:32           ` Wolfgang Denk
2006-01-16 10:08             ` Marco Roeland
  -- strict thread matches above, loose matches on Subject: below --
2006-05-20 23:05 Dave Jones
     [not found] ` <20060520190802.0df67730.seanlkml@sympatico.ca>
2006-05-20 23:08   ` Sean
2006-05-20 23:19 ` Linus Torvalds
2006-05-20 23:49   ` Dave Jones

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=7v8xth14pg.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=wd@denx.de \
    /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).