From: "Lukas Sandström" <lukass@etek.chalmers.se>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <junkio@cox.net>,
"Lukas Sandström" <lukass@etek.chalmers.se>
Subject: Re: Remove unneeded packs
Date: Sun, 13 Nov 2005 11:58:11 +0100 [thread overview]
Message-ID: <43771C43.7000104@etek.chalmers.se> (raw)
In-Reply-To: <7voe4pclwm.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Lukas Sandström <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?
>
>
It depends on how expensive git-fsck-objects --full --unreacahble is versus
a full repack.
Howerver, if I read the source correctly git-fsck-objects doesn't currently test
the reachablility of packed objects. This would have to change, and I'm not certain
of how to do that properly.
Note that the following patch is reqired if git-repack -a -d is to work as expected.
(Remove all packs except the new one)
Btw, I'm sending this patch in utf8, let's see if it works...
----
Subject: [PATCH] Make sure all old packfiles are removed when doing a full repack
This is nessecary because unrachable objects in packfiles makes git-pack-redundant
flag them as non-redundant.
Signed-off-by: Lukas Sandström <lukass@etek.chalmers.se>
---
git-repack.sh | 16 +++++++++++++++-
1 files changed, 15 insertions(+), 1 deletions(-)
applies-to: 9a0f0c748316751fbf593a21f2b16bcdd975095a
08df1f641bd3f98a607a8413d647667adc18a633
diff --git a/git-repack.sh b/git-repack.sh
index f347207..293bb50 100755
--- a/git-repack.sh
+++ b/git-repack.sh
@@ -32,6 +32,8 @@ case ",$all_into_one," in
rev_list=
rev_parse='--all'
pack_objects=
+ existing=`cd "$PACKDIR" && \
+ find . -type f \( -name '*.pack' -o -name '*.idx' \) -print`
;;
esac
if [ "$local" ]; then
@@ -60,7 +62,19 @@ mv .tmp-pack-$name.pack "$PACKDIR/pack-$
mv .tmp-pack-$name.idx "$PACKDIR/pack-$name.idx" ||
exit
-if test "$remove_redandant" = t
+if test "$all_into_one" = t
+then
+ sync
+ ( cd "$PACKDIR" &&
+ for e in $existing
+ do
+ case "$e" in
+ ./pack-$name.pack | ./pack-$name.idx) ;;
+ *) rm -f $e ;;
+ esac
+ done
+ )
+else if test "$remove_redandant" = t
then
sync
redundant=$(git-pack-redundant --all)
---
0.99.9.GIT
next prev parent reply other threads:[~2005-11-13 10:57 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
2005-11-13 10:58 ` Lukas Sandström [this message]
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=43771C43.7000104@etek.chalmers.se \
--to=lukass@etek.chalmers.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).