From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: What's cooking in git.git (Oct 2018, #02; Sat, 13)
Date: Fri, 12 Oct 2018 17:02:21 +0200 [thread overview]
Message-ID: <878t33dx8i.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqh8hr9pxb.fsf@gitster-ct.c.googlers.com>
On Fri, Oct 12 2018, Junio C Hamano wrote:
> * ab/gc-doc-update (2018-10-11) 1 commit
> - gc doc: mention the commit-graph in the intro
>
> The documentation of "git gc" has been updated to mention that it
> is no longer limited to "pruning away crufts" but also updates
> ancillary files like commit-graph as a part of repository
> optimization.
>
> Waiting for reactions.
> cf. <20181010193818.20399-1-avarab@gmail.com>
> The author seems to feel that this might be controversial.
Probably shouldn't have mentioned that. SZEDER I think had more issues
with the "that's not GC" parts of what git-gc is doing, so I'll let him
chime in. I'm working on a more general update to gc.c which might bring
it more in the "not really GC anymore" direction.
But this patch is just describing the status quo, so I think it should
be uncontroversial to merge it, or at least we can have the discussion
about what we should do in a different venue than a doc fixup for
accurately describing what we're doing now.
Another topic: As noted in <20181010193235.17359-1-avarab@gmail.com> and
this follow-up
https://public-inbox.org/git/87h8hsexdm.fsf@evledraar.gmail.com/ it
would be great if you could pick up the "gc: remove redundant check for
gc_auto_threshold" patch. A small change that makes later refactoring a
tiny bit smaller and easier to understand.
next prev parent reply other threads:[~2018-10-12 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 14:53 What's cooking in git.git (Oct 2018, #02; Sat, 13) Junio C Hamano
2018-10-12 15:02 ` Ævar Arnfjörð Bjarmason [this message]
2018-10-12 19:44 ` Stefan Beller
2018-10-12 23:37 ` Stefan Beller
2018-10-13 1:03 ` Junio C Hamano
2018-10-15 17:32 ` Stefan Beller
2018-10-16 21:20 ` Josh Steadmon
2018-10-16 23:11 ` Junio C Hamano
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=878t33dx8i.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.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).