threads / patch / 32434

patch, 3 partsMove api-command.txt from ./technical/ to ./howto

Subject: [PATCH 0/3] Move api-command.txt from ./technical/ to ./howto

## tl;dr

5 messages between Dec 21, 2012 and Dec 21, 2012. Diffs are folded; open one to read it.

replies: 4people: 2as markdown or json

Thomas Ackermann· Dec 21, 2012, 18:02 UTC · lore

"api-command.txt" describes a different kind of API than the other api-* documents. So better move it to the howto documents in ./Documentation/howto and rename to "new-command.txt".

[PATCH 1/3] Move ./technical/api-command.txt to ./howto/new-command.txt [PATCH 2/3] Add new-command.txt to ./Documentation/Makefile [PATCH 3/3] Amend new-command.txt to be processed correctly by howto-index.sh

Signed-off-by: Thomas Ackermann <th.acker@arcor.de>

--- Thomas

Thomas Ackermann· Dec 21, 2012, 18:05 UTC · re: Thomas Ackermann · lore

[PATCH 1/3] Move ./technical/api-command.txt to ./howto/new-command.txt

Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/{technical/api-command.txt => howto/new-command.txt} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename Documentation/{technical/api-command.txt => howto/new-command.txt} (100%)
Show changes to Documentation/technical/api-command.txt +0 −0
diff --git a/Documentation/technical/api-command.txt b/Documentation/howto/new-command.txt
similarity index 100%
rename from Documentation/technical/api-command.txt
rename to Documentation/howto/new-command.txt
-- 
1.8.0.msysgit.0


---
Thomas
Thomas Ackermann· Dec 21, 2012, 18:06 UTC · re: Thomas Ackermann · lore

[PATCH 2/3] Add new-command.txt to ./Documentation/Makefile

Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/Makefile | 1 +
 1 file changed, 1 insertion(+)
Show changes to Documentation/Makefile +1 −0
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 7df75d0..f3afcb6 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -21,6 +21,7 @@ ARTICLES += git-tools
 ARTICLES += git-bisect-lk2009
 # with their own formatting rules.
 SP_ARTICLES = user-manual
+SP_ARTICLES += howto/new-command
 SP_ARTICLES += howto/revert-branch-rebase
 SP_ARTICLES += howto/using-merge-subtree
 SP_ARTICLES += howto/using-signed-tag-in-pull-request
-- 
1.8.0.msysgit.0


---
Thomas
Thomas Ackermann· Dec 21, 2012, 18:07 UTC · re: Thomas Ackermann · lore

[PATCH 3/3] Amend new-command.txt to be processed correctly by howto-index.sh

Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/howto/new-command.txt | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)
Show changes to Documentation/howto/new-command.txt +7 −2
diff --git a/Documentation/howto/new-command.txt b/Documentation/howto/new-command.txt
index d3b9781..36502f6 100644
--- a/Documentation/howto/new-command.txt
+++ b/Documentation/howto/new-command.txt
@@ -1,5 +1,10 @@
-Integrating new subcommands
-===========================
+From: Eric S. Raymond <esr@thyrsus.com>
+Abstract: This is how-to documentation for people who want to add extension
+ commands to git.  It should be read alongside api-builtin.txt.
+Content-type: text/asciidoc
+
+How to integrate new subcommands
+================================
 
 This is how-to documentation for people who want to add extension
 commands to git.  It should be read alongside api-builtin.txt.
-- 
1.8.0.msysgit.0


---
Thomas
Junio C Hamano· Dec 21, 2012, 18:33 UTC · re: Thomas Ackermann · lore

Re: [PATCH 0/3] Move api-command.txt from ./technical/ to ./howto

Thomas Ackermann <th.acker@arcor.de> writes:
Show 9 quoted lines
> "api-command.txt" describes a different kind of API than the other api-* documents.
> So better move it to the howto documents in ./Documentation/howto and rename
> to "new-command.txt".
>
> [PATCH 1/3] Move ./technical/api-command.txt to ./howto/new-command.txt
> [PATCH 2/3] Add new-command.txt to ./Documentation/Makefile
> [PATCH 3/3] Amend new-command.txt to be processed correctly by howto-index.sh
>
> Signed-off-by: Thomas Ackermann <th.acker@arcor.de>

Seems good from a cursory look, but I think this is better done in a single patch. If you do not mind, I'll squash them into one.

Thanks.

← back to recent threads