From: Petr Baudis <pasky@suse.cz>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: pack count on repo.or.cz [was "Medium term dreams"]
Date: Wed, 3 Sep 2008 12:08:28 +0200 [thread overview]
Message-ID: <20080903100828.GS10360@machine.or.cz> (raw)
In-Reply-To: <48BD446C.6020403@viscovery.net>
On Tue, Sep 02, 2008 at 03:49:32PM +0200, Johannes Sixt wrote:
> Petr Baudis schrieb:
> >> As to why the other packs weren't pruned, I don't know. In my example,
> >> you can see that the pruning happens as we expect. So either there is a
> >> bug in git-prune-packed, or there is something we're not realizing.
> >
> > Well, that's my question here. :-)
>
> Does removing all the *.keep files help? ;)
Haha, good catch - thanks! :-) I wonder where they came from, though I
hazily remember some curious behaviour of older Git versions wrt. .keep
files and they seem all to be of old date. Now I have a single nice pack
and fsck of all the forks still passes fine.
Thanks all, I will adopt this for all projects.
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
next prev parent reply other threads:[~2008-09-03 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 23:19 Medium term dreams Junio C Hamano
2008-09-02 0:00 ` pack count on repo.or.cz [was "Medium term dreams"] Jeff King
2008-09-02 1:04 ` Petr Baudis
2008-09-02 1:14 ` Jeff King
2008-09-02 1:47 ` pack count on repo.or.cz Junio C Hamano
2008-09-02 1:56 ` Jeff King
2008-09-02 11:15 ` pack count on repo.or.cz [was "Medium term dreams"] Petr Baudis
2008-09-02 11:54 ` Jeff King
2008-09-02 13:08 ` Petr Baudis
2008-09-02 13:49 ` Johannes Sixt
2008-09-03 10:08 ` Petr Baudis [this message]
2008-09-04 5:33 ` Medium term dreams Mike Hommey
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=20080903100828.GS10360@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=peff@peff.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).