From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>
Subject: [PATCH] CONTRIBUTING: Accept patches in attachments
Date: Fri, 22 Dec 2023 12:10:36 +0100 [thread overview]
Message-ID: <20231222111014.9663-2-alx@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
I use mutt(1), which works fine with patches as attachments, and the
mailing list archives also work fine with attachments. Let's accept
attachments.
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
Any objections?
CONTRIBUTING | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/CONTRIBUTING b/CONTRIBUTING
index ef531231d..b1374fe10 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -128,9 +128,7 @@ Description
- from a mailing list or online forum? Please provide a URL
if possible.
- - Send patches in diff -u format, inline inside the email
- message. If you're worried about your mailer breaking the
- patch, the send it both inline and as an attachment. You may
+ - Send patches in diff -u format in an email patch. You may
find it useful to employ git-send-email(1) and
git-format-patch(1).
--
2.43.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2023-12-22 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231222111014.9663-2-alx@kernel.org \
--to=alx@kernel.org \
--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