Re: [PATCH 00/59] Split config.txt
- From
Stefan Beller <sbeller@google.com>
- Date
- Oct 22, 2018, 19:22 UTC
- Message-ID
- <CAGZ79kZyjjG9oRzC4jJ4ZqD2efkzR5GyFHUkZKf=811emE=tHA@mail.gmail.com>
- In-Reply-To
- <20181020123848.2785-1-pclouds@gmail.com>
On Sat, Oct 20, 2018 at 5:39 AM Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote:
Show 15 quoted lines
> > 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. config.txt is now about the > syntax, and a list of config sections. http section can be moved out > later. > > I did a doc-diff on this series and the only change is ssh.variant is > moved down a bit to keep it in order, which is intended. > > I thought of grouping all these config files in a separate directory > Documentation/config to avoid cluttering Documentation/ too much but > let's wait and see if people really find Documentation growing too > large first.
Have you considered to use config as a prefix, i.e. have config-add.txt instead of add-config.txt ?
currently any command is documented in a file that is prefixed with "git-". There are others such as gitcli or gitsubmodules, but as they lack the '-' they surely are not about a command.
With the config- prefix it would be easier to sort and cope with the individual files, and it would allow grepping through Documentation/conf* (which may be easier than Documentation/*conf* or similar)
I have no strong objection to the series as is (I have not looked at any patch), but I would think either a config directory or prefix may help further.
Stefan