public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Linux Man-Pages <linux-man@vger.kernel.org>
Subject: Re: [PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC
Date: Mon, 6 Feb 2023 11:47:21 +0100	[thread overview]
Message-ID: <16bed7ee-0b58-078b-4a25-9ed85748801f@gmail.com> (raw)
In-Reply-To: <85435ead-0573-340f-56a2-4dda1990b20c@Shaw.ca>


[-- Attachment #1.1: Type: text/plain, Size: 1745 bytes --]

Hi Brian,

On 2/6/23 05:46, Brian Inglis wrote:
> On 2023-02-05 17:02, Alejandro Colomar wrote:
>> On 2/6/23 00:31, Alejandro Colomar wrote:
>> Could you please send the patches inline?
> 
>>> If you fear that your mailer might break them, send them _also_ attached, but 
>>> please send them inline in the email.
> 
>> Also, please send git patches, with a commit message, which can be produced 
>> with git-format-patch(1).
> 
> I did my usual:
> $ sed -i -e '
> s!^...$!...!
>      ...
> '
> $ ...
> $ git commit -m 'man2/...' man2/...
> # 11 commits: 9 individual 8 files, 1 interval notation 6 files, 1 rest 33 files
> $ git format-patch ... -11
> $ git send-email ... 00??-...

Hmm, I thought you had sent it with something else, since I had never seen 
git-format-patch create such an email, but in fact it can.  I guess you use 
--attach=... or have it configured in your git config.  Could you please create 
the patch with git format-patch --no-attach ... ?

> 
> Saw no need for longer multi-line commit messages as each was pretty specific.
> Please say if you prefer a different patch format or convention.
> 
> Do you expect some other email client than git to be used to send email, or do 
> you just want all the patch diffs in a single email body or what?

No, in fact I expect git with default settings :)

> 
> Some patches may be delayed or disjoint as my ISP email is aggressively filtered 
> by an outsourced "provider" that does not like patch series in or out and fails 
> with no status code: "<from...> server temporarily unavailable. AUP#MXRT"!


Cheers,

Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-06 10:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 22:59 [PATCH 00/11] man2/: punctuate long numeric strings with digit separators Brian Inglis
2023-02-05 22:59 ` [PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC Brian Inglis
2023-02-05 23:31   ` Alejandro Colomar
2023-02-06  0:02     ` Alejandro Colomar
2023-02-06  4:46       ` Brian Inglis
2023-02-06 10:47         ` Alejandro Colomar [this message]
2023-02-06  0:05   ` Alejandro Colomar
2023-02-05 22:59 ` [PATCH 02/11] man2/spu_run.2: fix example comment status code or-ed value Brian Inglis
2023-02-05 22:59 ` [PATCH 03/11] man2/: use consistent interval notation for value ranges Brian Inglis
2023-02-05 22:59 ` [PATCH 04/11] man2/open.2: punctuate octal perms with digit separators Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2023-02-07 20:11 man2/: punctuate long numeric strings " Brian Inglis
2023-02-07 20:11 ` [PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC Brian Inglis
2023-02-07 23:44   ` Alejandro Colomar
2023-02-08  3:58     ` Brian Inglis
2023-02-08 10:59       ` Alejandro Colomar
2023-02-08 14:06         ` Brian Inglis
2023-02-08 20:58           ` Brian Inglis
2023-02-08 21:13             ` Alejandro Colomar
2023-02-07 20:32 [PATCH 00/11] man2/: punctuate long numeric strings with digit separators Brian Inglis
2023-02-07 20:32 ` [PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC Brian Inglis

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=16bed7ee-0b58-078b-4a25-9ed85748801f@gmail.com \
    --to=alx.manpages@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