From: Junio C Hamano <junkio@cox.net>
To: Lukas =?iso-2022-jp-2?B?U2FuZHN0chsuQRtOdm0=?= <lukass@etek.chalmers.se>
Cc: git@vger.kernel.org
Subject: Re: Remove unneeded packs
Date: Sat, 12 Nov 2005 18:38:17 -0800 [thread overview]
Message-ID: <7voe4pclwm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <43766687.2000007@etek.chalmers.se> (Lukas =?iso-2022-jp-2?B?U2FuZHN0chsuQRtOdm0ncw==?= message of "Sat, 12 Nov 2005 23:02:47 +0100")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 558 bytes --]
Lukas Sandstr^[.A^[Nvm <lukass@etek.chalmers.se> writes:
> This is most likley because the pack b3c6... contains unreachable objects.
> git-pack-redundant only makes sure that all objects present in packfiles
> still are present in packfiles after the redundant packs have been removed.
> ...
> I'm thinking of the possibility passing a list of objects to be ignored
> on stdin to git-pack-redundant. This would hopefully solve this problem.
But once you go down that path, wouldn't doing 'repack -a -d'
become looking simpler and more attractive, I wonder?
next prev parent reply other threads:[~2005-11-13 2:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 13:04 Remove unneeded packs Marcel Holtmann
2005-11-12 13:13 ` Andreas Ericsson
2005-11-12 13:30 ` Marcel Holtmann
2005-11-12 22:02 ` Lukas Sandström
2005-11-12 22:13 ` Marcel Holtmann
2005-11-13 2:38 ` Junio C Hamano [this message]
2005-11-13 10:58 ` Lukas Sandström
2005-11-13 12:00 ` Sergey Vlasov
2005-11-13 12:07 ` Lukas Sandström
2005-11-13 12:20 ` Sergey Vlasov
2005-11-13 12:31 ` Lukas Sandström
2005-11-12 13:40 ` Craig Schlenter
2005-11-12 13:59 ` Balanced packing strategy Petr Baudis
2005-11-12 15:14 ` Craig Schlenter
2005-11-13 2:34 ` Junio C Hamano
2005-11-13 11:00 ` Petr Baudis
2005-11-13 20:06 ` Josef Weidendorfer
2005-11-13 23:13 ` Junio C Hamano
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=7voe4pclwm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=lukass@etek.chalmers.se \
/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).