Re: Recommended configurations (was Re: [PATCH v1 2/2] reset: add new reset.quietDefault config setting)

From: Jeff King <peff@peff.net>
Date: Oct 24, 2018, 23:58 UTC
Message-ID: <20181024235813.GA1399@sigill.intra.peff.net>
In-Reply-To: <29db5fed-4556-277e-7aad-7ff3233550a9@gmail.com>

On Wed, Oct 24, 2018 at 11:48:20AM -0400, Derrick Stolee wrote:

Show 13 quoted lines

> Generally, there are a lot of config settings that are likely in the "if you
> have a big repo, then you should use this" category. However, there is
> rarely a one-size-fits-all solution to these problems, just like there are
> different ways a repo can be "big" (working directory? number of commits?
> submodules?).
> [...]
> All of this is to say: it is probably a good idea to have some "recommended
> configuration" for big repos, but there will always be power users who want
> to tweak each and every one of these settings. I'm open to design ideas of
> how to store a list of recommended configurations and how to set a group of
> config settings with one command (say, a "git recommended-config
> [small|large|submodules]" builtin that fills the local config with the
> important settings).

Maybe it would be useful to teach git-sizer[1] to recommend particular settings based on the actual definitions of "big" that it measures.

I do hope that some options will just be no-brainers to enable always, though (e.g., I think in the long run commit-graph should just default to "on"; it's cheap to keep up to date and helps proportionally to the repo size).

[1] https://github.com/github/git-sizer