Move ./technical/api-command.txt to ./howto/new-command.txt
The contents of this document does not describe any particular API, but is more about the way to add a new command, which belongs to the "How To" section of the documentation suite. Signed-off-by: Thomas Ackermann <th.acker@arcor.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thomas Ackermann committed
Dec 21, 2012 at 19:05 UTC
81670e9bfcd8a24410cf16f4362c720f950f61d4
2 files changed
+8
-2
Documentation/Makefile
+1
@@ -21,6 +21,7 @@ ARTICLES += git-tools
21
ARTICLES += git-bisect-lk2009
22
# with their own formatting rules.
23
SP_ARTICLES = user-manual
24
+SP_ARTICLES += howto/new-command
25
SP_ARTICLES += howto/revert-branch-rebase
26
SP_ARTICLES += howto/using-merge-subtree
27
SP_ARTICLES += howto/using-signed-tag-in-pull-request
Documentation/howto/new-command.txt
renamed
+7
-2
@@ -1,5 +1,10 @@
1
-Integrating new subcommands
2
-===========================
1
+From: Eric S. Raymond <esr@thyrsus.com>
2
+Abstract: This is how-to documentation for people who want to add extension
3
+ commands to git. It should be read alongside api-builtin.txt.
4
+Content-type: text/asciidoc
5
+
6
+How to integrate new subcommands
7
+================================
8
9
This is how-to documentation for people who want to add extension
10
commands to git. It should be read alongside api-builtin.txt.