Thread (14 messages) flat view 14 messages, 2 authors, 2016-06-15
STALE3741d

Revision v5 of 4 in this series.

Revisions (4)
  1. v5 current
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v7 [diff vs current]

[PATCH v5 5/6] new-command.txt: mention the common command groups

From: Sébastien Guimmara <hidden>
Date: 2016-06-15 23:04:42
Subsystem: documentation, the rest · Maintainers: Jonathan Corbet, Linus Torvalds

In the 6. step, add information about the common group commands
found in command-list.txt.

Signed-off-by: Sébastien Guimmara <redacted>
---
 Documentation/howto/new-command.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt
index d7de5a3..e7b0cc2 100644
--- a/Documentation/howto/new-command.txt
+++ b/Documentation/howto/new-command.txt
@@ -95,7 +95,9 @@ your language, document it in the INSTALL file.
 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
-in the main directory.
+in the main directory. If the new command is part of the typical Git
+workflow and you believe it's common enough to be mentioned in
+'git help', map this command to a common group in the column [common]
 
 7. Give the maintainer one paragraph to include in the RelNotes file
 to describe the new feature; a good place to do so is in the cover
-- 
2.4.0
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help