From: Junio C Hamano <gitster@pobox.com>
To: Firmin Martin <firminmartin24@gmail.com>
Cc: git@vger.kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>,
"J. Bruce Fields" <bfields@citi.umich.edu>
Subject: Re: [PATCH v2 1/1] user-manual.txt: assign preface an id and a title
Date: Sat, 03 Apr 2021 23:21:31 -0700 [thread overview]
Message-ID: <xmqqr1jqy3h0.fsf@gitster.g> (raw)
In-Reply-To: <20210404040739.2671960-2-firminmartin24@gmail.com> (Firmin Martin's message of "Sun, 4 Apr 2021 06:07:39 +0200")
Firmin Martin <firminmartin24@gmail.com> writes:
> -<preface>
> -<title></title>
> +<preface id="_introduction">
> +<title>Introduction</title>
Makes sense.
> -@node Top, idm4, , (dir)
> +@node Top, Introduction, , (dir)
and of course this looks nicer.
> @documentlanguage en
> @top Git User Manual
>
> @menu
> -* : idm4.
> +* Introduction::
so does this.
And the side effects on other formats are ...
> --- before/user-manual.html.md 2021-04-04 05:20:55.378695854 +0200
> +++ after/user-manual.html.md 2021-04-04 05:21:11.282850802 +0200
> @@ -4,6 +4,8 @@
>
> **Table of Contents**
>
> +Introduction
> +
> 1\. Repositories and Branches
>
>
> @@ -278,7 +280,7 @@
>
> Todo list
>
> -#
> +# Introduction
>
> Git is a fast distributed revision control system.
>
> --- before/user-manual.pdf.txt 2021-04-04 05:28:20.367036836 +0200
> +++ after/user-manual.pdf.txt 2021-04-04 05:30:01.680026312 +0200
> @@ -487,6 +487,7 @@
>
> vii
>
> +Introduction
> Git is a fast distributed revision control system.
> This manual is designed to be readable by someone with basic UNIX command-line skills, but no previous knowledge of Git.
> Chapter 1 and Chapter 2 explain how to fetch and study a project using git—read these chapters to learn how to build and test a
... all sensible.
> Signed-off-by: Firmin Martin <firminmartin24@gmail.com>
> ---
> Documentation/user-manual.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
> index fd480b8645..f9e54b8674 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -1,5 +1,8 @@
> = Git User Manual
>
> +[preface]
> +== Introduction
> +
> Git is a fast distributed revision control system.
>
> This manual is designed to be readable by someone with basic UNIX
Thanks, will queue.
next prev parent reply other threads:[~2021-04-04 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 12:13 [PATCH][GSoC] user-manual.txt: fix empty heading of introduction Firmin Martin
2021-04-02 21:22 ` Junio C Hamano
2021-04-02 21:29 ` Junio C Hamano
2021-04-02 22:23 ` Junio C Hamano
2021-04-03 5:16 ` Bagas Sanjaya
2021-04-04 0:46 ` Junio C Hamano
2021-04-04 4:07 ` [PATCH v2 0/1] user-manual.txt: assign preface an id and a title Firmin Martin
2021-04-04 4:07 ` [PATCH v2 1/1] " Firmin Martin
2021-04-04 6:21 ` Junio C Hamano [this message]
2021-04-04 4:31 ` [PATCH v2 0/1] " Firmin Martin
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=xmqqr1jqy3h0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=bfields@citi.umich.edu \
--cc=firminmartin24@gmail.com \
--cc=git@vger.kernel.org \
/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).