From: Duy Nguyen <pclouds@gmail.com>
Date: Sat, 20 Oct 2018 19:30:14 GMT
Subject: Re: [PATCH 00/59] Split config.txt
Message-ID: <CACsJy8ADfhRk9eUJG+FE4k_D5sZvBOu47Vm4Gkae1XiOVtZyjQ@mail.gmail.com>
In-Reply-To: <87d0s4ctds.fsf@evledraar.gmail.com>

On Sat, Oct 20, 2018 at 9:25 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> And sometimes like in the case of git-gc(1) we have gc.* config
> documented in two places with different prose that needs to be updated
> in two places in a CONFIGURATION section. This series allows us to just
> unify the two and do an "include" in two places, and more generally have
> the convention that a given command that uses configuration could have
> that config both documented in git-config(1), and the same docs in its
> own manpage.
>
> Is doing some post-cleanup like that your eventual goal after this
> series?

I did see the possibility of including command-specific config in
individual command man page. But I'm not planning on doing it myself.
Some command man page is already pretty long, plus sometimes we rely
on the core.* part which should not be included in per-command man
page...
-- 
Duy