Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Apr 6, 2019, 19:28 UTC
- Message-ID
- <87h8bb9bmx.fsf@evledraar.gmail.com>
- In-Reply-To
- <xmqqr2aidpxw.fsf@gitster-ct.c.googlers.com>
On Thu, Apr 04 2019, Junio C Hamano wrote:
Just comments on ab/* stuff:
Show 12 quoted lines
> * ab/gc-reflog (2019-04-01) 7 commits > - gc: handle & check gc.reflogExpire config > - reflog tests: assert lack of early exit with expiry="never" > - reflog tests: test for the "points nowhere" warning > - reflog tests: make use of "test_config" idiom > - gc: refactor a "call me once" pattern > - gc: convert to using the_hash_algo > - gc: remove redundant check for gc_auto_threshold > > Fix various glitches in "git gc" around reflog handling. > > cf. <20190328161434.19200-1-avarab@gmail.com> (v4)
Missing a "will..." note for this one, the "cf" is just the cover letter for v4. AFAICT it should be ready to merge down from "pu".
Show 13 quoted lines
> * ab/gc-docs (2019-04-01) 12 commits > - SQAUSH??? fixup! gc docs: include the "gc.*" section from "config" in "gc" > - gc docs: remove incorrect reference to gc.auto=0 > - gc docs: clarify that "gc" doesn't throw away referenced objects > - gc docs: note "gc --aggressive" in "fast-import" > - gc docs: downplay the usefulness of --aggressive > - gc docs: note how --aggressive impacts --window & --depth > - gc docs: fix formatting for "gc.writeCommitGraph" > - gc docs: re-flow the "gc.*" section in "config" > - gc docs: include the "gc.*" section from "config" in "gc" > - gc docs: clean grammar for "gc.bigPackThreshold" > - gc docs: stop noting "repack" flags > - gc docs: modernize the advice for manually running "gc"
That squash makes sense. Will submit another version with it integrated.