git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Firmin Martin <firminmartin24@gmail.com>
To: Firmin Martin <firminmartin24@gmail.com>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2 0/1] user-manual.txt: assign preface an id and a title
Date: Sun,  4 Apr 2021 06:07:38 +0200	[thread overview]
Message-ID: <20210404040739.2671960-1-firminmartin24@gmail.com> (raw)
In-Reply-To: <20210402121303.344914-1-firminmartin24@gmail.com>

I found a more satisfying way to keep the change minimal: it turns out that
[preface] does exactly what we want. It just adds the missing id and the title.
No renumbering, etc.

See https://docs.asciidoctor.org/asciidoc/latest/sections/preface/

I attached the diff of user-manual.xml, user-manual.texi, git.info,
user-manual.html (using html2markdown) and user-manual.pdf (using
pdftotext) in the commit message which I also reworded and shortened.

Firmin Martin (1):
  user-manual.txt: assign preface an id and a title

 Documentation/user-manual.txt | 3 +++
 1 file changed, 3 insertions(+)

-- 
2.31.1.133.g84d06cdc06


  parent reply	other threads:[~2021-04-04  4:09 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 ` Firmin Martin [this message]
2021-04-04  4:07   ` [PATCH v2 1/1] user-manual.txt: assign preface an id and a title Firmin Martin
2021-04-04  6:21     ` Junio C Hamano
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=20210404040739.2671960-1-firminmartin24@gmail.com \
    --to=firminmartin24@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).