Re: What's cooking in git.git (Mar 2021, #03; Wed, 10)

>
>
> On Thu, Mar 11 2021, Junio C Hamano wrote:
>
> Some notes, mostly on my own topics:
>
> > * ab/tests-cleanup-around-sha1 (2021-03-10) 4 commits
> >  - tests: get rid of $_x05 from the test suite
> >  - shortlog tests: rewrite to get rid of --abbrev=35 hardcoding
> >  - test-lib: remove unused $_x40 and $_z40 variables
> >  - git-bisect: remove unused SHA-1 $x40 shell variable
>
> FWIW (mostly for other readers) I suggested in
> https://lore.kernel.org/git/87tupigf02.fsf@evledraar.gmail.com/ just now
> that we drop 4/4.
>
> I thought we had better testing for --abbrev (turns out only I do with
> local patches), so unrelated to this we've had some regressions in its
> handling due to lack of testing (which this would remove more of...).
>
> >  Will merge to 'next'.
> >  In the longer term, we might want to remove filter-branch and nudge
> >  folks to more modern tools.
>
> Did we ever have a re-discussion of adding Elijah's
> git-filter-replacement-whose-name-I-always-forget to git.git? :)
>
> > [...]
> > [Graduated to 'master']
> >
> > * jt/transfer-fsck-across-packs-fix (2021-03-05) 1 commit
> >   (merged to 'next' on 2021-03-07 at c79f295216)
> >  + fetch-pack: do not mix --pack_header and packfile uri
>
> LGTM, see below about ab/fsck-api-cleanup though...
>
> >  The code to fsck objects received across multiple packs during a
> >  single git fetch session has been broken when the packfile URI
> >  feature was in use.  A workaround has been added by disabling the
> >  codepath that avoids keeping a packfile that is too small.
> >
> > [...]
> > * hn/reftable (2021-03-08) 17 commits
> >  - SQUASH??? calloc(nmemb,size)
> >  - SQUASH??? allow t0031 to run with any default branch name
> >  - Add "test-tool dump-reftable" command.
> >  - git-prompt: prepare for reftable refs backend
> >  - Reftable support for git-core
> >  - reftable: rest of library
> >  - reftable: reftable file level tests
> >  - reftable: read reftable files
> >  - reftable: write reftable files
> >  - reftable: a generic binary tree implementation
> >  - reftable: reading/writing blocks
> >  - reftable: (de)serialization for the polymorphic record type.
> >  - reftable: add blocksource, an abstraction for random access reads
> >  - reftable: utility functions
> >  - reftable: add error related functionality
> >  - reftable: add LICENSE
> >  - init-db: set the_repository->hash_algo early on
>
> It would be nice to have a post-release revival of this, Han-Wen, any
> plans for that?