git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 (Jan 2022, #02; Wed, 5))
Date: Thu, 6 Jan 2022 11:54:23 -0500	[thread overview]
Message-ID: <Ydcev8HqCjycBJS+@nand.local> (raw)
In-Reply-To: <xmqq1r1lfwyq.fsf@gitster.g>

On Wed, Jan 05, 2022 at 05:56:45PM -0800, Junio C Hamano wrote:
> * tb/cruft-packs (2021-11-29) 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
>
>  Instead of leaving unreachable objects in loose form when packing,
>  or ejecting them into loose form when repacking, gather them in a
>  packfile with an auxiliary file that records the last-use time of
>  these objects.
>
>  Expecting a reroll.
>  cf. <865b99dd-0b18-9a07-49c1-3959a777c685@gmail.com>
>  cf. <c9437c89-9258-4034-9886-8a2aec46aa6b@gmail.com>
>  cf. <YaqiYGM48p5F9lS1@nand.local>
>  source: <cover.1638224692.git.me@ttaylorr.com>

Feel free to eject this for the time being, especially if it makes
managing your tree any more convenient. I have a few small things that I
want to adjust before sending a new version, which likely won't happen
until after we have finished the 2.35 cycle.

Thanks,
Taylor

  parent reply	other threads:[~2022-01-06 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06  1:56 What's cooking in git.git (Jan 2022, #02; Wed, 5) Junio C Hamano
2022-01-06 16:53 ` Taylor Blau
2022-01-06 16:54 ` Taylor Blau [this message]
2022-01-06 18:21   ` tb/cruft-packs 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Ydcev8HqCjycBJS+@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).