From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH/RFC 00/11] Break down Documentation/config.txt
Date: Wed, 22 Aug 2018 18:05:54 +0200 [thread overview]
Message-ID: <20180822160605.21864-1-pclouds@gmail.com> (raw)
I notice a couple times lately that people added new config keys in
the wrong place, which is understandable since this file has become so
big, it's hard to see the structure of anything.
Since we have broken down some parts of it into separate files
already, this continues in that direction and moves even more parts
out of config.txt.
I don't have a well defined criteria to decide which part should be
moved out. I just did it when I see a section is getting too big, or
becomes less relevant today, or not move to avoid conflicts on 'pu'.
But if this is a good move, we can discuss this further.
I group by section, but I think in some cases we can even do better
and group multiple sections in one file (which also means they are
rendered close together). This again is up to discussion.
Nguyễn Thái Ngọc Duy (11):
config.txt: follow camelCase naming
config.txt: move fetch part out to a separate file
config.txt: move format part out to a separate file
config.txt: move gitcvs part out to a separate file
config.txt: move gui part out to a separate file
config.txt: move pull part out to a separate file
config.txt: move push part out to a separate file
config.txt: move receive part out to a separate file
config.txt: move sendemail part out to a separate file
config.txt: move sequence.editor out of "core" part
config.txt: move submodule part out to a separate file
Documentation/config.txt | 720 +----------------------------
Documentation/fetch-config.txt | 65 +++
Documentation/format-config.txt | 87 ++++
Documentation/gitcvs-config.txt | 67 +++
Documentation/gui-config.txt | 57 +++
Documentation/pull-config.txt | 36 ++
Documentation/push-config.txt | 113 +++++
Documentation/receive-config.txt | 123 +++++
Documentation/sendemail-config.txt | 63 +++
Documentation/submodule-config.txt | 82 ++++
10 files changed, 711 insertions(+), 702 deletions(-)
create mode 100644 Documentation/fetch-config.txt
create mode 100644 Documentation/format-config.txt
create mode 100644 Documentation/gitcvs-config.txt
create mode 100644 Documentation/gui-config.txt
create mode 100644 Documentation/pull-config.txt
create mode 100644 Documentation/push-config.txt
create mode 100644 Documentation/receive-config.txt
create mode 100644 Documentation/sendemail-config.txt
create mode 100644 Documentation/submodule-config.txt
--
2.19.0.rc0.335.ga73d156e9c
next reply other threads:[~2018-08-22 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 16:05 Nguyễn Thái Ngọc Duy [this message]
2018-08-22 16:05 ` [PATCH 01/11] config.txt: follow camelCase naming Nguyễn Thái Ngọc Duy
2018-08-22 16:05 ` [PATCH 02/11] config.txt: move fetch part out to a separate file Nguyễn Thái Ngọc Duy
2018-08-22 16:05 ` [PATCH 03/11] config.txt: move format " Nguyễn Thái Ngọc Duy
2018-08-22 16:05 ` [PATCH 04/11] config.txt: move gitcvs " Nguyễn Thái Ngọc Duy
2018-08-22 16:05 ` [PATCH 05/11] config.txt: move gui " Nguyễn Thái Ngọc Duy
2018-08-22 16:06 ` [PATCH 06/11] config.txt: move pull " Nguyễn Thái Ngọc Duy
2018-08-22 16:06 ` [PATCH 07/11] config.txt: move push " Nguyễn Thái Ngọc Duy
2018-08-22 16:06 ` [PATCH 08/11] config.txt: move receive " Nguyễn Thái Ngọc Duy
2018-08-22 16:06 ` [PATCH 09/11] config.txt: move sendemail " Nguyễn Thái Ngọc Duy
2018-08-22 16:06 ` [PATCH 10/11] config.txt: move sequence.editor out of "core" part Nguyễn Thái Ngọc Duy
2018-08-22 16:06 ` [PATCH 11/11] config.txt: move submodule part out to a separate file Nguyễn Thái Ngọc Duy
2018-08-22 16:28 ` [PATCH/RFC 00/11] Break down Documentation/config.txt 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=20180822160605.21864-1-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
/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).