From: Dave Wolfe <dwolfe@lists.linuxppc.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Correct way to submit a patch?
Date: Mon, 4 Feb 2002 14:25:03 -0600 [thread overview]
Message-ID: <20020204142503.A20449@lists.linuxppc.org> (raw)
In-Reply-To: <20020204004850.24542@mailhost.mipsys.com>; from benh@kernel.crashing.org on Mon, Feb 04, 2002 at 01:48:49AM +0100
[ benh@kernel.crashing.org writes: ]
>
> The proper way is to send it to this list, eventually CC'ed to one
> of the people in the MAINTAINERS file depending which type of machine
> is affected by it.
I would suggest that patches be attached to the email. Attachments
can be easily saved off as files, whereas inlined patches must be
extracted from the rest of the message and often get mangled by MUAs.
This is particularly true when trying to retrieve patches from the HTML
archives. Ideally such attachments would also be encoded or use some
other means to prevent them from being mangled during mail transport.
Also note that once you hit 20 or 30 Kb, it's not a patch, so please
don't try to send it to the list. Put it on an FTP or web server and
mail the URL to the list, or mail it privately to the maintainers.
--
Dave Wolfe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-04 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 7:43 Correct way to submit a patch? David Müller (ELSOFT AG)
2002-02-04 0:48 ` benh
2002-02-04 15:17 ` Tom Rini
2002-02-04 20:25 ` Dave Wolfe [this message]
2002-02-05 16:18 ` Tom Rini
2002-02-05 16:25 ` hollis
2002-02-05 9:04 ` Armin
2002-02-05 17:23 ` Dave Wolfe
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=20020204142503.A20449@lists.linuxppc.org \
--to=dwolfe@lists.linuxppc.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).