From: "George Spelvin" <linux@horizon.com>
To: git@vger.kernel.org
Cc: linux@horizon.com, peff@peff.net
Subject: Re: git auto-repack is broken...
Date: 3 Dec 2011 01:55:19 -0500 [thread overview]
Message-ID: <20111203065519.22213.qmail@science.horizon.com> (raw)
Thanks, Jeff, for the life-cycle chart.
A couple of ideas come to mind:
- When unpacking objects from a pack, it should be fine to set their
date to that of the pack. After all, they're at least that old.
- We could put unreferenced objects into packs whose date is the most
recent of any of the contained objects.
- We could then group unreferenced objects into packs based on age,
so their ages sould not be affected too much by the preceding
operations.
That still produces a noticeable number of packs, which isn't
good, but maybe it's better that keeping thousands of loose
objects for a month...
next reply other threads:[~2011-12-03 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 6:55 George Spelvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-02 16:22 git auto-repack is broken Linus Torvalds
2011-12-02 16:27 ` Ævar Arnfjörð Bjarmason
2011-12-02 16:56 ` Linus Torvalds
2011-12-02 17:10 ` Jeff King
2011-12-02 17:35 ` Junio C Hamano
2011-12-02 17:45 ` Jeff King
2011-12-02 18:08 ` Junio C Hamano
2011-12-02 18:13 ` Jeff King
2011-12-03 19:42 ` Brandon Casey
2011-12-07 22:12 ` Nicolas Pitre
2011-12-07 22:53 ` Jeff King
2011-12-08 0:18 ` Nicolas Pitre
2011-12-08 0:45 ` Jeff King
2011-12-08 3:35 ` Nicolas Pitre
2011-12-08 3:40 ` Jeff King
2011-12-09 17:35 ` Junio C Hamano
2011-12-09 18:34 ` Nicolas Pitre
2011-12-08 0:49 ` Jeff King
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=20111203065519.22213.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--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).