aboutsummaryrefslogtreecommitdiff
path: root/Documentation/technical
diff options
context:
space:
mode:
authorThomas Ackermann <th.acker@arcor.de>2012-12-15 09:29:07 +0100
committerJunio C Hamano <gitster@pobox.com>2012-12-15 10:46:47 -0800
commitfef11965da875c105c40f1a9550af1f5e34a6e62 (patch)
tree1d2a83f2c6c2a09d1ba4d141e02a9dcdef557e55 /Documentation/technical
parentbfae342c973b0be3c9e99d3d86ed2e6b152b4a6b (diff)
downloadgit-fef11965da875c105c40f1a9550af1f5e34a6e62.tar.gz
git-fef11965da875c105c40f1a9550af1f5e34a6e62.tar.xz
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>
Diffstat (limited to 'Documentation/technical')
-rw-r--r--Documentation/technical/api-command.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/technical/api-command.txt b/Documentation/technical/api-command.txt
index ea9b2eda3..d3b978177 100644
--- a/Documentation/technical/api-command.txt
+++ b/Documentation/technical/api-command.txt
@@ -71,28 +71,28 @@ Integrating a command
Here are the things you need to do when you want to merge a new
subcommand into the git tree.
-0. Don't forget to sign off your patch!
+1. Don't forget to sign off your patch!
-1. Append your command name to one of the variables BUILTIN_OBJS,
+2. Append your command name to one of the variables BUILTIN_OBJS,
EXTRA_PROGRAMS, SCRIPT_SH, SCRIPT_PERL or SCRIPT_PYTHON.
-2. Drop its test in the t directory.
+3. Drop its test in the t directory.
-3. If your command is implemented in an interpreted language with a
+4. If your command is implemented in an interpreted language with a
p-code intermediate form, make sure .gitignore in the main directory
includes a pattern entry that ignores such files. Python .pyc and
.pyo files will already be covered.
-4. If your command has any dependency on a particular version of
+5. If your command has any dependency on a particular version of
your language, document it in the INSTALL file.
-5. There is a file command-list.txt in the distribution main directory
+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-cmmands.txt
in the main directory.
-6. Give the maintainer one paragraph to include in the RelNotes file
+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
letter [PATCH 0/n].