Renumber list in api-command.txt
Start list with 1 instead of 0; ASCIIDOC will renumber it anyway. Signed-off-by: Thomas Ackermann <th.acker@arcor.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thomas Ackermann committed
Dec 15, 2012 at 09:29 UTC
fef11965da875c105c40f1a9550af1f5e34a6e62
1 file changed
+7
-7
Documentation/technical/api-command.txt
+7
-7
@@ -71,28 +71,28 @@ Integrating a command
71
Here are the things you need to do when you want to merge a new
72
subcommand into the git tree.
73
74
-0. Don't forget to sign off your patch!
74
+1. Don't forget to sign off your patch!
75
76
-1. Append your command name to one of the variables BUILTIN_OBJS,
76
+2. Append your command name to one of the variables BUILTIN_OBJS,
77
EXTRA_PROGRAMS, SCRIPT_SH, SCRIPT_PERL or SCRIPT_PYTHON.
78
79
-2. Drop its test in the t directory.
79
+3. Drop its test in the t directory.
80
81
-3. If your command is implemented in an interpreted language with a
81
+4. If your command is implemented in an interpreted language with a
82
p-code intermediate form, make sure .gitignore in the main directory
83
includes a pattern entry that ignores such files. Python .pyc and
84
.pyo files will already be covered.
85
86
-4. If your command has any dependency on a particular version of
86
+5. If your command has any dependency on a particular version of
87
your language, document it in the INSTALL file.
88
89
-5. There is a file command-list.txt in the distribution main directory
89
+6. There is a file command-list.txt in the distribution main directory
90
that categorizes commands by type, so they can be listed in appropriate
91
subsections in the documentation's summary command list. Add an entry
92
for yours. To understand the categories, look at git-cmmands.txt
93
in the main directory.
94
95
-6. Give the maintainer one paragraph to include in the RelNotes file
95
+7. Give the maintainer one paragraph to include in the RelNotes file
96
to describe the new feature; a good place to do so is in the cover
97
letter [PATCH 0/n].
98