Skip to content

Commit 81670e9

Browse files
tacker66gitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent fef1196 commit 81670e9

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

Documentation/Makefile

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ ARTICLES += git-tools
2121
ARTICLES += git-bisect-lk2009
2222
# with their own formatting rules.
2323
SP_ARTICLES = user-manual
24+
SP_ARTICLES += howto/new-command
2425
SP_ARTICLES += howto/revert-branch-rebase
2526
SP_ARTICLES += howto/using-merge-subtree
2627
SP_ARTICLES += howto/using-signed-tag-in-pull-request

Documentation/technical/api-command.txt renamed to Documentation/howto/new-command.txt

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
1-
Integrating new subcommands
2-
===========================
1+
From: Eric S. Raymond <[email protected]>
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+
================================
38

49
This is how-to documentation for people who want to add extension
510
commands to git. It should be read alongside api-builtin.txt.

0 commit comments

Comments
 (0)