git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[Patch] Renumber list in api-command.txt

From
Thomas Ackermann <th.acker@arcor.de>
Date
Dec 15, 2012, 08:29 UTC
Message-ID
<683281078.296628.1355560147606.JavaMail.ngmail@webmail08.arcor-online.net>
In-Reply-To
<1479174763.154268.1350408444997.JavaMail.ngmail@webmail15.arcor-online.net>
- Start list with 1 instead of 0 because ASCIIDOC will renumber it anyway
Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/technical/api-command.txt | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/technical/api-command.txt b/Documentation/technical/api-command.txt
index ea9b2ed..d3b9781 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].
 
-- 
1.8.0.msysgit.0


---
Thomas
Previous: Junio C HamanoNext: Thomas Ackermann
Message 11 of 17 in “Create single PDF for all HTML files”
  1. 0/8 Create single PDF for all HTML filesThomas Ackermann, Oct 16, 2012
  2. 1/8 Split over-long synopsis in git-fetch-pack.txt into several linesThomas Ackermann, Oct 16, 2012
  3. 2/8 Shorten two over-long lines in git-bisect-lk2009.txt by abbreviating some sha1Thomas Ackermann, Oct 16, 2012
  4. 3/8 Change headline of technical/send-pack-pipeline.txt to not confuse its content with content from git-send-pack.txtThomas Ackermann, Oct 16, 2012
  5. 4/8 Prerequisites for creating nice html for all files in Documentation/technicalThomas Ackermann, Oct 16, 2012
  6. 5/8 Prerequisites for creating nice html for all files in Documentation/howtoThomas Ackermann, Oct 16, 2012
  7. 6/8 Prerequisites for creating nice html for all files in Documentation/RelNotesThomas Ackermann, Oct 16, 2012
  8. 7/8 Create pdf from all html filesThomas Ackermann, Oct 16, 2012
  9. 8/8 Wire everything into Makefile and Documentation/MakefileThomas Ackermann, Oct 16, 2012
  10. Junio C HamanoOct 16, 2012
  11. Renumber list in api-command.txtThomas Ackermann, Dec 15, 2012
  12. Remove misleading date form api-index-skel.txtThomas Ackermann, Dec 16, 2012
  13. Andreas SchwabDec 16, 2012
  14. Junio C HamanoDec 16, 2012
  15. Move api-command.txt to the end of API list in api-index.txtThomas Ackermann, Dec 16, 2012
  16. Junio C HamanoDec 16, 2012
  17. Aw: Re: [PATCH] Move api-command.txt to the end of API list in api-index.txtThomas Ackermann, Dec 17, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.