From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Thaddeus H. Black" <thb@debian.org>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v3] filename.7: new manual page
Date: Tue, 19 Oct 2021 15:38:09 +0200 [thread overview]
Message-ID: <22573673-bf1e-0f64-7e95-6cf0a23c2015@gmail.com> (raw)
In-Reply-To: <YW2hzL5vDfVZIAXY@b-tk.org>
Hi Thaddeus,
On 10/18/21 6:33 PM, Thaddeus H. Black wrote:
> Please find patch v3 below, via "git format-patch".
> (If the format is still wrong, or if there is some other way
> in which I should better support the team's work flow, kindly advise.)
'git format-patch' is the preferred method :)
What I missed here is the long (and great) commit message from v1, which
I'm going to save as the commit message. Please, when you send v4,
include the original text.
Ephemeral stuff that should not go into the commit message (like
changelogs between versions of the patch), you can put it above, in a
"scissor patch" format (see git-format-patch(1) if necessary).
Or if it's short/simple enough, below the '---' (and just above the
patch itself; it is actually ignored by git, unless it's so complex that
it is misinterpreted as part of the patch). This method is what I
usually use, since it doesn't require specifying '--scissors', and I
usually only write normal text that can't be confused with the patch. I
don't know if this is documented anywhere, but it's very useful.
Thanks,
Alex
>
> ---------------------------------------------------------------------------
> CHANGES IN v3
> ---------------------------------------------------------------------------
>
> Thaddeus H. Black (3):
> Polish prose under "Special semantics"
> Polish and clarify prose under "Letter case"
> Clarify the final paragraph under "Locales and Unicode"
>
> ---------------------------------------------------------------------------
> CHANGES IN v2
> ---------------------------------------------------------------------------
>
> Hendrik Boom, G. Branden Robinson and Alejandro Colomar (1):
> Write "uppercase" and "lowercase" rather than "capital" and "small"
>
> Alejandro Colomar and G. Branden Robinson (2):
> Use semantic newlines
> Avoid \f, but rather use separate lines
>
> Alejandro Colomar (11):
> Use subsections instead of sections
> Use subsubsections instead of subsections
> Remove unnecessary .P after .S[HS]
> Use .PP rather than .P
> Fix indentation of paragraph, which continues talking about \0
> Mention FAT
> For consistency, list "-" with "-name" and ".name"; s/a pair of/some/
> Delete the redundant mention of "."
> By s/all but/almost/, avoid double negation
> Reference filesystems(5) under SEE ALSO
> Under CONFORMING TO, write only, "POSIX.1‐2001 and later."
>
> G. Branden Robinson (3):
> Write "letter case" rather than "capitalization"
> Reference section-3 pages not under SEE ALSO but only in passing
> Avoid \c
>
> Thaddeus H. Black (2):
> Reword subsubsect "Special semantics" to support Alejandro's change no. 7
> Avoid beginning any subsect or subsubsect with specially formatted text
>
> ---------------------------------------------------------------------------
> GROFF SOURCE v3 (IN GIT'S PATCH FORMAT)
> ---------------------------------------------------------------------------
>
> ---
Here you can write your patch changelogs.
> man7/filename.7 | 660 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 660 insertions(+)
> create mode 100644 man7/filename.7
>
> diff --git a/man7/filename.7 b/man7/filename.7
> new file mode 100644
> index 000000000..9c53f8c7b
> --- /dev/null
> +++ b/man7/filename.7
> @@ -0,0 +1,660 @@
> +.\" Copyright (C) 2021 Thaddeus H. Black <thb@debian.org>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-10-19 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 23:07 [PATCH v2] filename.7: new manual page Thaddeus H. Black
2021-10-18 16:25 ` Thaddeus H. Black
2021-10-18 16:33 ` [PATCH v3] " Thaddeus H. Black
2021-10-19 8:54 ` Florian Weimer
2021-10-19 11:05 ` Thaddeus H. Black
2021-10-19 13:55 ` Alejandro Colomar (man-pages)
2021-10-20 8:12 ` Florian Weimer
2021-10-21 12:18 ` Thaddeus H. Black
2021-10-19 13:38 ` Alejandro Colomar (man-pages) [this message]
2021-11-07 14:36 ` Thaddeus H. Black
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=22573673-bf1e-0f64-7e95-6cf0a23c2015@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=thb@debian.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