On Sat, Oct 20, 2018 at 5:39 AM Nguyễn Thái Ngọc Duy wrote:
>
> I started this a couple months back, moving a couple big config
> sections out of config.txt to make it more manageable. This series
> almost completes that. It moves all configs (except http.* which have
> changes on 'pu') out of con
On Sun, Oct 21, 2018 at 1:29 AM Junio C Hamano wrote:
>
> Ævar Arnfjörð Bjarmason writes:
>
> > I had a slight bias against this when you started this, since I'm one of
> > these odd people who don't mind ~20k line files if the line count isn't
> > contributing to inherent complexity, e.g. in the
Ævar Arnfjörð Bjarmason writes:
> I had a slight bias against this when you started this, since I'm one of
> these odd people who don't mind ~20k line files if the line count isn't
> contributing to inherent complexity, e.g. in the case of config.txt you
> could just use the search function all i
On Sat, Oct 20 2018, Duy Nguyen wrote:
> On Sat, Oct 20, 2018 at 9:25 PM Ævar Arnfjörð Bjarmason
> 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. Thi
On Sat, Oct 20, 2018 at 9:25 PM Ævar Arnfjörð Bjarmason
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
On Sat, Oct 20 2018, Nguyễn Thái Ngọc Duy wrote:
> I started this a couple months back, moving a couple big config
> sections out of config.txt to make it more manageable. This series
> almost completes that. It moves all configs (except http.* which have
> changes on 'pu') out of config.txt. co
6 matches
Mail list logo
