aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-07-28 11:25:57 -0700
committerJunio C Hamano <gitster@pobox.com>2016-07-28 11:25:57 -0700
commitdcfb9d7d30720f50c6e66a85d5a96edc3151e9bf (patch)
tree7f1e47d7b1630ed687d2ea8c31ef83fffb933138 /Documentation
parent87be95b6f9c51c0492f48e30fd14316934a7e3c8 (diff)
parent82f6178af6d8a54718c7f45977622f96af9e6f95 (diff)
downloadgit-dcfb9d7d30720f50c6e66a85d5a96edc3151e9bf.tar.gz
git-dcfb9d7d30720f50c6e66a85d5a96edc3151e9bf.tar.xz
Merge branch 'nd/doc-new-command' into maint
Typofix in a doc. * nd/doc-new-command: new-command.txt: correct the command description file
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/howto/new-command.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt
index 6d772bd92..15a4c8031 100644
--- a/Documentation/howto/new-command.txt
+++ b/Documentation/howto/new-command.txt
@@ -94,7 +94,7 @@ your language, document it in the INSTALL file.
6. There is a file command-list.txt in the distribution main directory
that categorizes commands by type, so they can be listed in appropriate
subsections in the documentation's summary command list. Add an entry
-for yours. To understand the categories, look at git-commands.txt
+for yours. To understand the categories, look at command-list.txt
in the main directory. If the new command is part of the typical Git
workflow and you believe it common enough to be mentioned in 'git help',
map this command to a common group in the column [common].