git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)
Date: Mon, 08 Apr 2019 13:18:54 +0900	[thread overview]
Message-ID: <xmqqef6db041.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <87h8bb9bmx.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sat, 06 Apr 2019 21:28:22 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> 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".

The former is because I haven't decided and more importantly I
haven't seen enough input on the list to make a decision.

The latter is quite normal.  cf. is literally "here is one of the
things I can look at as a starting point to remind me what this
topic was about and what its current state is", a note left for me.
It often is "don't forget that somebody raised an issue and I should
not merge to to 'next' yet" but it is not limited to objections.

As I haven't seen enough input on the topic, and I have quite a
backlog after being offline for a wee, pointing at a cover to make
sure I can quickly find out which iteration I happen to have was/is
a logical thing to do.

>> * 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.

OK, then I won't squash it myself, but instead queue the updated
patches.

Thanks.

  reply	other threads:[~2019-04-08  4:18 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
2019-04-08  4:18   ` Junio C Hamano [this message]
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=xmqqef6db041.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    /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).