From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: tb/cruft-packs (was Re: What's cooking in git.git (May 2022, #07; Wed, 25))
Date: Thu, 26 May 2022 14:08:57 -0400 [thread overview]
Message-ID: <Yo/CObnqie21V2Mg@nand.local> (raw)
In-Reply-To: <xmqqzgj41ya2.fsf@gitster.g>
On Thu, May 26, 2022 at 01:41:25AM -0700, Junio C Hamano wrote:
> * tb/cruft-packs (2022-05-25) 18 commits
> - sha1-file.c: don't freshen cruft packs
> - builtin/gc.c: conditionally avoid pruning objects via loose
> - builtin/repack.c: add cruft packs to MIDX during geometric repack
> - builtin/repack.c: use named flags for existing_packs
> - builtin/repack.c: allow configuring cruft pack generation
> - builtin/repack.c: support generating a cruft pack
> - builtin/pack-objects.c: --cruft with expiration
> - reachable: report precise timestamps from objects in cruft packs
> - reachable: add options to add_unseen_recent_objects_to_traversal
> - builtin/pack-objects.c: --cruft without expiration
> - builtin/pack-objects.c: return from create_object_entry()
> - t/helper: add 'pack-mtimes' test-tool
> - pack-mtimes: support writing pack .mtimes files
> - chunk-format.h: extract oid_version()
> - pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles'
> - fixup! pack-mtimes: support reading .mtimes files
> - pack-mtimes: support reading .mtimes files
> - Documentation/technical: add cruft-packs.txt
>
> A mechanism to pack unreachable objects into a "cruft pack",
> instead of ejecting them into loose form to be reclaimed later, has
> been introduced.
>
> Will merge to 'next' after squashing fixup! in???
> source: <cover.1653088640.git.me@ttaylorr.com>
I think this is ready. This topic has been thoroughly reviewed, and the
outstanding topics:
- user-facing documentation cautioning about mixed-version cruft GCs
(similar to what I added in Documentation/technical/cruft-packs.txt
in v4)
- 64-bit timestamps, if desired
Can easily be done on top. The first one is trivial, and I'll send
some patches before getting too close to the -rc phase. The latter is
more substantial, but isn't a requirement for merging this (and the
format is extensible so this could be done on top if there is
significant interest).
Thanks,
Taylor
next prev parent reply other threads:[~2022-05-26 18:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 8:41 What's cooking in git.git (May 2022, #07; Wed, 25) Junio C Hamano
2022-05-26 16:02 ` Victoria Dye
2022-05-26 17:23 ` Junio C Hamano
2022-05-26 18:02 ` Ævar Arnfjörð Bjarmason
2022-05-26 18:30 ` Victoria Dye
2022-05-26 18:40 ` Ævar Arnfjörð Bjarmason
2022-05-26 23:10 ` Junio C Hamano
2022-05-26 18:08 ` Taylor Blau [this message]
2022-05-26 18:10 ` Taylor Blau
2022-05-26 20:17 ` Junio C Hamano
2022-05-26 18:11 ` tb/midx-race-in-pack-objects (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:49 ` sg/build-gitweb (was: " Ævar Arnfjörð Bjarmason
2022-05-26 19:06 ` sg/build-gitweb Junio C Hamano
2022-05-26 18:51 ` jc/http-clear-finished-pointer (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:37 ` Re* jc/http-clear-finished-pointer Junio C Hamano
2022-05-27 20:41 ` Johannes Schindelin
2022-05-27 21:35 ` Junio C Hamano
2022-06-01 7:26 ` Ævar Arnfjörð Bjarmason
2022-06-01 15:48 ` Junio C Hamano
2022-05-26 18:54 ` js/bisect-in-c (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:38 ` js/bisect-in-c Junio C Hamano
2022-05-26 20:00 ` js/bisect-in-c Junio C Hamano
2022-05-27 12:52 ` js/bisect-in-c Ævar Arnfjörð Bjarmason
2022-05-26 18:57 ` jx/l10n-workflow-change (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
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=Yo/CObnqie21V2Mg@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).