From: Daniel White <daniel@whitehouse.id.au>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: [StGit PATCH] Fixes for auto-generation of man pages
Date: Tue, 9 Sep 2008 17:17:21 +1000 [thread overview]
Message-ID: <20080909171721.2c7974a1@whitehouse.id.au> (raw)
In-Reply-To: <20080908210811.1957.16419.stgit@yoghurt>
stg.txt is the only man page not generated by stg-build --commands.
Provide this page explicitly instead of including all other
commands twice.
stg-cmd-list.txt is only a template for inclusion in other man
pages, so rename to stop it being built along with other stg-*
files.
Signed-off-by: Daniel White <daniel@whitehouse.id.au>
---
Documentation/.gitignore | 1 +
Documentation/Makefile | 6 +++---
Documentation/stg.txt | 2 +-
3 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/Documentation/.gitignore b/Documentation/.gitignore
index 32dd09d..c72f35c 100644
--- a/Documentation/.gitignore
+++ b/Documentation/.gitignore
@@ -3,3 +3,4 @@
*.[1-9]
stg-*.txt
doc.dep
+command-list.txt
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 85e9600..165e222 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -1,7 +1,7 @@
COMMANDS = $(shell ../stg-build --commands)
COMMANDS_TXT = $(patsubst %,stg-%.txt,$(COMMANDS))
-MAN1_TXT=$(wildcard stg*.txt) $(COMMANDS_TXT)
+MAN1_TXT= stg.txt $(COMMANDS_TXT)
DOC_HTML=$(patsubst %.txt,%.html,$(MAN1_TXT))
@@ -60,14 +60,14 @@ doc.dep : $(wildcard *.txt) build-docdep.perl
-include doc.dep
clean:
- rm -f *.xml *.html *.pdf *.1 doc.dep $(COMMANDS_TXT) stg-cmd-list.txt
+ rm -f *.xml *.html *.pdf *.1 doc.dep $(COMMANDS_TXT) command-list.txt
ALL_PY = $(shell find ../stgit -name '*.py')
$(COMMANDS_TXT): $(ALL_PY)
../stg-build --asciidoc $(basename $(subst stg-,,$@)) > $@
-stg-cmd-list.txt: $(ALL_PY)
+command-list.txt: $(ALL_PY)
../stg-build --cmd-list > $@
%.html : %.txt
diff --git a/Documentation/stg.txt b/Documentation/stg.txt
index b4184b2..d8f7d01 100644
--- a/Documentation/stg.txt
+++ b/Documentation/stg.txt
@@ -105,7 +105,7 @@ description is available in individual command manpages. Those
manpages are named 'stg-<command>(1)'.
endif::backend-docbook[]
-include::stg-cmd-list.txt[]
+include::command-list.txt[]
CONFIGURATION MECHANISM
-----------------------
--
1.6.0.1.220.g80d1
next prev parent reply other threads:[~2008-09-09 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 21:07 [StGit PATCH 0/3] Auto-generate man pages and command list Karl Hasselström
2008-09-08 21:08 ` [StGit PATCH 2/3] asciidoc.conf: Steal updates from git Karl Hasselström
2008-09-08 21:08 ` [StGit PATCH 3/3] Generate command lists automatically Karl Hasselström
2008-09-09 7:17 ` Daniel White [this message]
2008-09-10 15:56 ` [StGit PATCH] Fixes for auto-generation of man pages Karl Hasselström
[not found] ` <20080908210758.1957.664.stgit@yoghurt>
2008-09-10 21:56 ` [StGit PATCH 1/3] Auto-generate man pages for all StGit commands Catalin Marinas
2008-09-11 6:58 ` Karl Hasselström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080909171721.2c7974a1@whitehouse.id.au \
--to=daniel@whitehouse.id.au \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).