From: "Philip Oakley" <philipoakley@iee.org>
To: "Thomas Ackermann" <th.acker66@arcor.de>, <git@vger.kernel.org>
Subject: Re: [Patch 2/5] Create html documents for all files in Documentation/technical
Date: Sat, 6 Oct 2012 19:45:11 +0100 [thread overview]
Message-ID: <3662216A9D714C08B8522340D420AEEA@PhilipOakley> (raw)
In-Reply-To: 652323221.269712.1349538906380.JavaMail.ngmail@webmail08.arcor-online.net
From: "Thomas Ackermann" <th.acker66@arcor.de>
>- add missing files
> - fix some asciidoc layout problems
>
> Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
> ---
> Documentation/Makefile | 12 ++++++++++-
> Documentation/technical/index-format.txt | 2 +-
> Documentation/technical/pack-format.txt | 8 +++----
> Documentation/technical/pack-protocol.txt | 7 +++---
> Documentation/technical/shallow.txt | 8 ++++++-
> Documentation/technical/trivial-merge.txt | 36
> +++++++++++++++----------------
> 6 files changed, 45 insertions(+), 28 deletions(-)
>
> diff --git a/Documentation/Makefile b/Documentation/Makefile
> index 267dfe1..86594f6 100644
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -25,6 +25,16 @@ SP_ARTICLES += howto/revert-branch-rebase
> SP_ARTICLES += howto/using-merge-subtree
> SP_ARTICLES += howto/using-signed-tag-in-pull-request
> API_DOCS = $(patsubst %.txt,%,$(filter-out
> technical/api-index-skel.txt technical/api-index.txt, $(wildcard
> technical/api-*.txt)))
> +API_DOCS += technical/index-format
Would it not be better to create a separate TECH_DOCS list, rather than
confuse the API_DOCS list?
> +API_DOCS += technical/pack-format
> +API_DOCS += technical/pack-heuristics
> +API_DOCS += technical/pack-protocol
> +API_DOCS += technical/protocol-capabilities
> +API_DOCS += technical/protocol-common
> +API_DOCS += technical/racy-git
> +API_DOCS += technical/send-pack-pipeline
> +API_DOCS += technical/shallow
> +API_DOCS += technical/trivial-merge
> SP_ARTICLES += $(API_DOCS)
> SP_ARTICLES += technical/api-index
>
> @@ -231,7 +241,7 @@ clean:
> $(RM) *.texi *.texi+ *.texi++ git.info gitman.info
> $(RM) *.pdf
> $(RM) howto-index.txt howto/*.html doc.dep
> - $(RM) technical/api-*.html technical/api-index.txt
> + $(RM) technical/*.html technical/api-index.txt
> $(RM) $(cmds_txt) *.made
> $(RM) manpage-base-url.xsl
>
> diff --git a/Documentation/technical/index-format.txt
> b/Documentation/technical/index-format.txt
> index 9d25b30..57d6f91 100644
> --- a/Documentation/technical/index-format.txt
> +++ b/Documentation/technical/index-format.txt
> @@ -1,7 +1,7 @@
> GIT index format
> ================
>
> -= The git index file has the following format
> +== The git index file has the following format
>
<snip>
next prev parent reply other threads:[~2012-10-06 18:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 15:51 [Patch 0/5] Create single PDF for all HTML files Thomas Ackermann
2012-10-06 15:53 ` [Patch 1/5] Fix some asciidoc layout problems Thomas Ackermann
2012-10-06 18:39 ` Junio C Hamano
2012-10-06 19:10 ` Jeff King
2012-10-07 8:01 ` Aw: " Thomas Ackermann
2012-10-06 15:55 ` [Patch 2/5] Create html documents for all files in Documentation/technical Thomas Ackermann
2012-10-06 18:45 ` Philip Oakley [this message]
2012-10-06 15:55 ` [Patch 3/5] Create html documents for all files in Documentation/RelNotes Thomas Ackermann
2012-10-06 18:48 ` Philip Oakley
2012-10-06 19:21 ` Jeff King
2012-10-07 20:53 ` Junio C Hamano
2012-10-15 11:48 ` Michael J Gruber
2012-10-15 20:49 ` Junio C Hamano
2012-10-06 15:57 ` [Patch 4/5] Create html documents for all files in Documentation/howto Thomas Ackermann
2012-10-06 15:58 ` [Patch 5/5] Create pdf from all html files Thomas Ackermann
2012-10-06 19:11 ` Jeff King
2012-10-06 19:32 ` [Patch 0/5] Create single PDF for all HTML files Jeff King
2012-10-07 20:54 ` Junio C Hamano
2012-10-07 8:14 ` Aw: " Thomas Ackermann
2012-10-07 22:52 ` Jeff King
2012-10-15 11:55 ` Michael J Gruber
2012-10-15 17:42 ` Jeff King
2012-10-08 22:53 ` Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3662216A9D714C08B8522340D420AEEA@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=th.acker66@arcor.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).