From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man-pages(7): Add attributive annotation advice
Date: Thu, 20 Jul 2023 10:24:18 +0200 [thread overview]
Message-ID: <b8431b23-4554-6e1b-c3da-817d153e1ca5@kernel.org> (raw)
In-Reply-To: <20230720021311.2wyrt5tlglsxcl3a@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 930 bytes --]
On 2023-07-20 04:13, G. Branden Robinson wrote:
> At 2023-07-19T22:01:35+0200, Alejandro Colomar wrote:
>> I'm now doubting the necessity of this patch. It's like very
>> obvious content when you already know what it talks about, and
>> not very clear until you know what it's talking about. Maybe
>> following existing practice is just simpler.
>
> Okay. I withdraw it.
>
> (Also, waiting to see if my 275 KiB inline patch to "unbracket tables"
> comes through. How should I get it to this list if it doesn't?)
A gzip works, although in such cases of scripted patches, you can
just send the header of the patch, and maybe the first pages to
allow me to check the results of the script, and then I will
reproduce the patch myself by running the script.
Cheers,
Alex
>
> Regards,
> Branden
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-20 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 4:18 [PATCH] man-pages(7): Add attributive annotation advice G. Branden Robinson
2023-07-19 20:01 ` Alejandro Colomar
2023-07-20 2:13 ` G. Branden Robinson
2023-07-20 8:24 ` Alejandro Colomar [this message]
2023-07-20 9:14 ` G. Branden Robinson
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=b8431b23-4554-6e1b-c3da-817d153e1ca5@kernel.org \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.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