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:
OpenPGP_signature
Description: OpenPGP digital signature
