Break down Documentation/config.txt
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest11 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/11 | config.txt: follow camelCase namingDocumentation/ | +1 | 0 replies | |
| 2/11 | config.txt: move fetch part out to a separate fileDocumentation/ Documentation/ | +66 | 0 replies | |
| 3/11 | config.txt: move format part out to a separate fileDocumentation/ Documentation/ | +88 | 0 replies | |
| 4/11 | config.txt: move gitcvs part out to a separate fileDocumentation/ Documentation/ | +68 | 0 replies | |
| 5/11 | config.txt: move gui part out to a separate fileDocumentation/ Documentation/ | +58 | 0 replies | |
| 6/11 | config.txt: move pull part out to a separate fileDocumentation/ Documentation/ | +37 | 0 replies | |
| 7/11 | config.txt: move push part out to a separate fileDocumentation/ Documentation/ | +114 | 0 replies | |
| 8/11 | config.txt: move receive part out to a separate fileDocumentation/ Documentation/ | +124 | 0 replies | |
| 9/11 | config.txt: move sendemail part out to a separate fileDocumentation/ Documentation/ | +64 | 0 replies | |
| 10/11 | config.txt: move sequence.editor out of "core" partDocumentation/ | +6 | 0 replies | |
| 11/11 | config.txt: move submodule part out to a separate fileDocumentation/ Documentation/ | +83 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH/RFC 00/11] Break down Documentation/config.txt
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
Signature · 1 line
2.19.0.rc0.335.ga73d156e9c