From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: git-repack && git-prune-packed isn't doing it's job anymore?
Date: Sat, 4 Mar 2006 13:29:52 +1300 [thread overview]
Message-ID: <46a038f90603031629qbbb287ckd8da1ef56a831dba@mail.gmail.com> (raw)
$ find .git/objects -type f | grep -v pack | wc -l
3297
$ git-repack && git-prune-packed
Generating pack...
Done counting 664 objects.
Deltifying 664 objects.
100% (664/664) done
Writing 664 objects.
100% (664/664) done
Total 664, written 664 (delta 384), reused 0 (delta 0)
Pack pack-f38c51a5d5194d6a2f6e711586b9a51980c8d524 created.
$ find .git/objects -type f | grep -v pack | wc -l
2583
Strange! This is from todays master,
$ git --version
git version 1.2.4.g0a60
cheers,
martin
next reply other threads:[~2006-03-04 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 0:29 Martin Langhoff [this message]
2006-03-04 0:53 ` git-repack && git-prune-packed isn't doing it's job anymore? Junio C Hamano
2006-03-04 1:01 ` Martin Langhoff
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=46a038f90603031629qbbb287ckd8da1ef56a831dba@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
/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).