From: Derrick Stolee <derrickstolee@github.com>
To: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Taylor Blau" <me@ttaylorr.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: tb/cruft-packs (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3))
Date: Fri, 4 Mar 2022 10:35:34 -0500 [thread overview]
Message-ID: <0870b8f0-976a-cf2f-f34f-7e966b9c426f@github.com> (raw)
In-Reply-To: <xmqqv8wu2vag.fsf@gitster.g>
On 3/3/2022 11:31 PM, Junio C Hamano wrote:
> * tb/cruft-packs (2022-03-02) 17 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'
> - 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'?
> source: <cover.1646266835.git.me@ttaylorr.com>
This version looks good to me. There were some other comments that
seem to have resolved without a need to change the patches.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-03-04 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 4:31 What's cooking in git.git (Mar 2022, #01; Thu, 3) Junio C Hamano
2022-03-04 13:25 ` ab/plug-random-leaks (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3)) Derrick Stolee
2022-03-04 18:33 ` Ævar Arnfjörð Bjarmason
2022-03-17 12:46 ` [PATCH] tests: test show --word-diff --color-moved Michael J Gruber
2022-03-17 14:55 ` [PATCH v2 0/2] diff.c: fix a recent memory leak regression Ævar Arnfjörð Bjarmason
2022-03-17 14:55 ` [PATCH v2 1/2] tests: demonstrate "show --word-diff --color-moved" regression Ævar Arnfjörð Bjarmason
2022-03-17 15:54 ` Junio C Hamano
2022-03-17 14:55 ` [PATCH v2 2/2] diff.c: fix a double-free regression in a18d66cefb Ævar Arnfjörð Bjarmason
2022-03-04 15:35 ` Derrick Stolee [this message]
2022-03-07 18:06 ` tb/cruft-packs (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3)) Jonathan Nieder
2022-03-07 18:18 ` Taylor Blau
2022-03-07 18:32 ` Derrick Stolee
2022-03-07 20:18 ` Jonathan Nieder
2022-03-07 20:51 ` Derrick Stolee
2022-03-07 21:34 ` Junio C Hamano
2022-03-08 0:52 ` Taylor Blau
2022-03-08 0:25 ` Junio C Hamano
2022-03-08 0:49 ` Taylor Blau
2022-03-05 14:25 ` jc/stash-drop (was: " Ævar Arnfjörð Bjarmason
2022-03-07 18:22 ` jc/stash-drop Junio C Hamano
2022-03-07 13:49 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3)) Derrick Stolee
2022-03-07 17:18 ` 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=0870b8f0-976a-cf2f-f34f-7e966b9c426f@github.com \
--to=derrickstolee@github.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).