tb/repack-expire-to (was: Re: What's cooking in git.git (Oct 2022, #07; Wed, 26))

From: Taylor Blau <me@ttaylorr.com>
Date: Oct 26, 2022, 19:42 UTC
Message-ID: <Y1mNp99PUPJAq4yc@nand.local>
In-Reply-To: <xmqqwn8mh1di.fsf@gitster.g>

On Wed, Oct 26, 2022 at 11:43:21AM -0700, Junio C Hamano wrote:

Show 11 quoted lines

> * tb/repack-expire-to (2022-10-24) 4 commits
>  - builtin/repack.c: implement `--expire-to` for storing pruned objects
>  - builtin/repack.c: write cruft packs to arbitrary locations
>  - builtin/repack.c: pass "cruft_expiration" to `write_cruft_pack`
>  - builtin/repack.c: pass "out" to `prepare_pack_objects`
>
>  "git repack" learns to send cruft objects out of the way into
>  packfiles outside the repository.
>
>  Will merge to 'next'?
>  source: <cover.1666636974.git.me@ttaylorr.com>

That would be great. There hasn't been a ton of review on this round, but there was a good set of eyes on it during the RFC phase where nobody seemed to complain loudly ;-).

So I'd be happy to see it get picked up, especially given its simplicity. But if you want to wait for more reviewers to look it over, that's fine too.

Thanks, Taylor