From: Alejandro Colomar <alx.manpages@gmail.com>
To: Brian.Inglis@Shaw.ca, Linux Man-Pages <linux-man@vger.kernel.org>
Subject: Re: [PATCH 00/11] man2/: punctuate long numeric strings with digit separators
Date: Wed, 8 Feb 2023 12:27:46 +0100 [thread overview]
Message-ID: <b51078f8-0424-0e1c-2fc0-e953a735b893@gmail.com> (raw)
In-Reply-To: <0a15e67d-536b-fc1d-54a9-ac942b8e8564@Shaw.ca>
[-- Attachment #1.1: Type: text/plain, Size: 1530 bytes --]
Hi Brian,
On 2/8/23 05:54, Brian Inglis wrote:
> Hi Alex,
>
> The problem was /etc/gitconfig [format] attach which is not invertible or
> overridable, expect perhaps with command line --inline: probably requested by
> some other project.
I never tried, but documentation says it's overridable:
--attach[=<boundary>]
Create multipart/mixed attachment, the first part of which is the
commit message and the patch itself in the second part, with
Content-Disposition: attachment.
--no-attach
Disable the creation of an attachment, overriding the configuration
setting.
Then there's
--inline[=<boundary>]
Create multipart/mixed attachment, the first part of which is the
commit message and the patch itself in the second part, with
Content-Disposition: inline.
but I'm not sure that's what I want. Never tried. Anyway, you can try any of both, and we'll see what arrives :)
>
> All patches 1-11 have identical content; MIME content-disposition is the issue;
> as is setting parameters to allow a single successful series of sends via my ISP
> milter provider that considers patch series as just more email spam.
No worries; I understand ;)
>
> I will retry format-patch with -v2 --inline and send-email with longer delays.
Okay, thanks.
Cheers,
Alex
>
--
<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-02-08 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2023-02-07 20:32 ` [PATCH 02/11] man2/spu_run.2: fix example comment status code or-ed value Brian Inglis
2023-02-07 20:32 ` [PATCH 03/11] man2/: use consistent interval notation for value ranges Brian Inglis
2023-02-07 20:32 ` [PATCH 04/11] man2/open.2: punctuate octal perms with digit separators Brian Inglis
2023-02-07 20:32 ` [PATCH 05/11] man2/reboot.2: show BCD dates in hex not decimal Brian Inglis
2023-02-07 20:32 ` [PATCH 06/11] man2/reboot.2: punctuate hex in docs with digit separators Brian Inglis
2023-02-07 20:32 ` [PATCH 07/11] man2/statfs.2: " Brian Inglis
2023-02-07 20:32 ` [PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs Brian Inglis
2023-02-07 20:32 ` [PATCH 09/11] man2/getrandom.2: change limit to use IEC suffix Brian Inglis
2023-02-07 20:32 ` [PATCH 10/11] man2/futex.2: change limit to use ISO suffix Brian Inglis
2023-02-07 20:33 ` [PATCH 11/11] man2/: punctuate long numeric strings with digit separators Brian Inglis
2023-02-07 23:49 ` [PATCH 00/11] " Alejandro Colomar
2023-02-08 4:54 ` Brian Inglis
2023-02-08 11:27 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-05 22:59 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=b51078f8-0424-0e1c-2fc0-e953a735b893@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Brian.Inglis@Shaw.ca \
--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