From: "Thaddeus H. Black" <thb@debian.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
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: Sun, 7 Nov 2021 14:36:50 +0000 [thread overview]
Message-ID: <YYfkggpiE1D+HW9R@b-tk.org> (raw)
In-Reply-To: <22573673-bf1e-0f64-7e95-6cf0a23c2015@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On Tue, Oct 19, 2021 at 03:38:09PM +0200, Alejandro Colomar (man-pages) wrote:
> '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.
Okay.
> 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.
In view of feedback, v4 requires substantial rewriting. Rewritten text
wants polishing. Polishing takes time.
In short, I haven't forgotten, but v4 is not yet ready.
Note to other readers: if any latecomers to the conversation wish to
suggest further significant changes, now would be the time to suggest;
for once the draft has been reassembled and repolished, it will be too
late. Nonsubscribers can find v3 at [1].
1: https://www.spinics.net/lists/linux-man/msg21267.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-11-07 15:21 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)
2021-11-07 14:36 ` Thaddeus H. Black [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=YYfkggpiE1D+HW9R@b-tk.org \
--to=thb@debian.org \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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