From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Stalled ds/ branches (was What's cooking in git.git (Apr 2019, #03; Tue, 16))
Date: Tue, 16 Apr 2019 12:25:14 -0400 [thread overview]
Message-ID: <e1329d06-2cfa-09b9-c3a8-69776a8fd777@gmail.com> (raw)
In-Reply-To: <xmqqef62ozny.fsf@gitster-ct.c.googlers.com>
On 4/16/2019 9:19 AM, Junio C Hamano wrote:
> * ds/midx-expire-repack (2019-01-27) 10 commits
> - midx: add test that 'expire' respects .keep files
> - multi-pack-index: test expire while adding packs
> - midx: implement midx_repack()
> - multi-pack-index: prepare 'repack' subcommand
> - multi-pack-index: implement 'expire' subcommand
> - midx: refactor permutation logic and pack sorting
> - midx: simplify computation of pack name lengths
> - multi-pack-index: prepare for 'expire' subcommand
> - Docs: rearrange subcommands for multi-pack-index
> - repack: refactor pack deletion for future use
>
> "git multi-pack-index expire/repack" are new subcommands that
> consult midx file and are used to drop unused pack files and
> coalesce small pack files that are still in use.
>
> Comments?
I'll be back to work full-time next week, and I have some ideas
to update this command. Specifically, the 'repack' command can
be improved in a few ways. I will elaborate on-thread when I
send a new version.
> * ds/commit-graph-format-v2 (2019-01-29) 8 commits
> - SQUASH : misnamed variables and style fix
> - commit-graph: test verifying a corrupt v2 header
> - commit-graph: implement file format version 2
> - commit-graph: add --version=<n> option
> - commit-graph: create new version flags
> - commit-graph: collapse parameters into flags
> - commit-graph: return with errors during write
> - Merge branch 'bc/sha-256' into ds/commit-graph-format-v2
>
> Introduce version 2 of the commit-graph format to correct
> deficiency in the initial version.
>
> Needs update before merging to 'next'.
Sorry for the issues colliding with other topics. I'll send a
new version next week that will resolve the conflicts. Hopefully
I can do this without needing to update the base commit.
Thanks,
-Stolee
next prev parent reply other threads:[~2019-04-16 16:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 13:19 What's cooking in git.git (Apr 2019, #03; Tue, 16) Junio C Hamano
2019-04-16 14:51 ` Ævar Arnfjörð Bjarmason
2019-04-16 15:26 ` Junio C Hamano
2019-04-17 7:18 ` Ævar Arnfjörð Bjarmason
2019-04-18 0:12 ` Junio C Hamano
2019-04-17 9:33 ` Duy Nguyen
2019-04-17 9:52 ` Phillip Wood
2019-04-17 10:22 ` Ævar Arnfjörð Bjarmason
2019-04-16 15:27 ` Ben Peart
2019-04-17 2:37 ` Junio C Hamano
2019-04-16 16:25 ` Derrick Stolee [this message]
2019-04-16 17:32 ` jt/clone-server-option (was What's cooking in git.git (Apr 2019, #03; Tue, 16)) Jonathan Tan
2019-04-17 2:39 ` Junio C Hamano
2019-04-17 16:18 ` Jonathan Tan
2019-04-18 1:51 ` Junio C Hamano
2019-04-17 2:37 ` What's cooking in git.git (Apr 2019, #03; Tue, 16) Taylor Blau
2019-04-17 5:38 ` Junio C Hamano
2019-04-17 5:42 ` Taylor Blau
2019-04-17 6:14 ` Junio C Hamano
2019-04-18 6:54 ` Taylor Blau
2019-04-17 12:50 ` jc/format-patch-error-check, was " Johannes Schindelin
2019-04-18 0:48 ` Junio C Hamano
2019-04-17 12:52 ` ab/test-lib-pass-trace2-env, " Johannes Schindelin
2019-04-18 0:19 ` Denton Liu
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=e1329d06-2cfa-09b9-c3a8-69776a8fd777@gmail.com \
--to=stolee@gmail.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).