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@xxxxxxxxxx>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
