From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)
Date: Sat, 06 Apr 2019 21:28:22 +0200 [thread overview]
Message-ID: <87h8bb9bmx.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqr2aidpxw.fsf@gitster-ct.c.googlers.com>
On Thu, Apr 04 2019, Junio C Hamano wrote:
Just comments on ab/* stuff:
> * 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".
> * 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.
next prev parent reply other threads:[~2019-04-06 19:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 10:28 What's cooking in git.git (Apr 2019, #01; Thu, 4) Junio C Hamano
2019-04-04 11:08 ` Duy Nguyen
2019-04-04 21:29 ` Junio C Hamano
2019-04-06 20:28 ` Ævar Arnfjörð Bjarmason
2019-04-08 4:14 ` Junio C Hamano
2019-04-09 10:26 ` [PATCH] Introduce "precious" file concept Nguyễn Thái Ngọc Duy
2019-04-09 11:31 ` Junio C Hamano
2019-04-10 9:36 ` Duy Nguyen
2019-04-12 1:28 ` Junio C Hamano
2019-04-09 17:44 ` Eric Sunshine
2019-04-12 21:54 ` Ævar Arnfjörð Bjarmason
2019-04-13 10:19 ` Duy Nguyen
2019-04-05 1:05 ` What's cooking in git.git (Apr 2019, #01; Thu, 4) Todd Zullinger
2019-04-05 5:41 ` Junio C Hamano
2019-04-06 19:28 ` Ævar Arnfjörð Bjarmason [this message]
2019-04-08 4:18 ` Junio C Hamano
2019-04-06 19:57 ` Ævar Arnfjörð Bjarmason
2019-04-08 4:28 ` Junio C Hamano
2019-04-08 21:18 ` Josh Steadmon
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=87h8bb9bmx.fsf@evledraar.gmail.com \
--to=avarab@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).