From: Junio C Hamano <gitster@pobox.com>
To: "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Jean-Noël Avila" <jn.avila@free.fr>
Subject: Re: [PATCH 0/2] Fix doc placeholders
Date: Tue, 26 Dec 2023 10:30:13 -0800 [thread overview]
Message-ID: <xmqqzfxwhl56.fsf@gitster.g> (raw)
In-Reply-To: <pull.1626.git.1703539287.gitgitgadget@gmail.com> ("Jean-Noël Avila via GitGitGadget"'s message of "Mon, 25 Dec 2023 21:21:25 +0000")
"Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com> writes:
> While setting up a check of (the absence of) translations of commands,
> options and environment variable in the manpages in the manpage translation
> project, some false positives appeared.
>
> Here is a series that enforces the formatting rules for placeholders in
> documentation and help.
Nice. Will take a look and then queue. Thanks.
>
> Jean-Noël Avila (2):
> doc: enforce dashes in placeholders
> doc: enforce placeholders in documentation
>
> Documentation/diff-options.txt | 2 +-
> Documentation/git-blame.txt | 2 +-
> Documentation/git-bugreport.txt | 4 ++--
> Documentation/git-commit-graph.txt | 2 +-
> Documentation/git-config.txt | 8 ++++----
> Documentation/git-cvsserver.txt | 4 ++--
> Documentation/git-daemon.txt | 10 +++++-----
> Documentation/git-diagnose.txt | 2 +-
> Documentation/git-difftool.txt | 2 +-
> Documentation/git-fast-import.txt | 4 ++--
> Documentation/git-fetch.txt | 4 ++--
> Documentation/git-filter-branch.txt | 6 +++---
> Documentation/git-format-patch.txt | 20 ++++++++++----------
> Documentation/git-mv.txt | 2 +-
> Documentation/git-notes.txt | 2 +-
> Documentation/git-replace.txt | 6 +++---
> Documentation/git-revert.txt | 4 ++--
> Documentation/git-send-email.txt | 2 +-
> Documentation/git-status.txt | 4 ++--
> Documentation/git-submodule.txt | 4 ++--
> Documentation/git-svn.txt | 18 +++++++++---------
> Documentation/git-tag.txt | 2 +-
> Documentation/git.txt | 4 ++--
> Documentation/gitdiffcore.txt | 8 ++++----
> Documentation/gitformat-index.txt | 4 ++--
> Documentation/githooks.txt | 8 ++++----
> Documentation/gitk.txt | 4 ++--
> Documentation/gitprotocol-capabilities.txt | 2 +-
> Documentation/gitprotocol-http.txt | 14 +++++++-------
> Documentation/gitprotocol-v2.txt | 8 ++++----
> Documentation/gitsubmodules.txt | 4 ++--
> Documentation/gitweb.conf.txt | 10 +++++-----
> Documentation/gitweb.txt | 2 +-
> Documentation/trace2-target-values.txt | 2 +-
> Documentation/urls.txt | 8 ++++----
> Documentation/user-manual.txt | 4 ++--
> builtin/commit-graph.c | 2 +-
> 37 files changed, 99 insertions(+), 99 deletions(-)
>
>
> base-commit: 564d0252ca632e0264ed670534a51d18a689ef5d
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1626%2Fjnavila%2Ffix_doc_placeholders-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1626/jnavila/fix_doc_placeholders-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/1626
prev parent reply other threads:[~2023-12-26 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 21:21 [PATCH 0/2] Fix doc placeholders Jean-Noël Avila via GitGitGadget
2023-12-25 21:21 ` [PATCH 1/2] doc: enforce dashes in placeholders Jean-Noël Avila via GitGitGadget
2023-12-25 21:21 ` [PATCH 2/2] doc: enforce placeholders in documentation Jean-Noël Avila via GitGitGadget
2023-12-26 18:30 ` Junio C Hamano [this message]
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=xmqqzfxwhl56.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jn.avila@free.fr \
/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).