From: Dave Wolfe <hidden> Date: 2002-02-04 20:25:03
[ 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/
On Tue, Feb 05, 2002 at 09:18:52AM -0700, Tom Rini wrote:
quoted
On Mon, Feb 04, 2002 at 02:25:03PM -0600, Dave Wolfe wrote:
quoted
[ benh@kernel.crashing.org writes: ]
quoted
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.
Please don't... I tend to take the Linus approach to this. I won't
ignore attachments like him tho.. :)
He makes a good point about list archives though... if the patch is inline,
you're left copying and pasting out of a web browser, which has all sorts of
formatting problems (like indentation, "<", etc).
If you send as an attachment (not gzipped, just plain text) then most mail
readers can read it inline *and* it will be saved in pristin form in the list
archives.
-Hollis
It seams to me that if I want someone else to check in my patch, I
certainly don't want to make more work for them. In my experience,
plain text does not all ways work.
armin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Mon, Feb 04, 2002 at 02:25:03PM -0600, Dave Wolfe wrote:
[ benh@kernel.crashing.org writes: ]
quoted
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.
On Tue, Feb 05, 2002 at 09:18:52AM -0700, Tom Rini wrote:
On Mon, Feb 04, 2002 at 02:25:03PM -0600, Dave Wolfe wrote:
quoted
[ benh@kernel.crashing.org writes: ]
quoted
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.
Please don't... I tend to take the Linus approach to this. I won't
ignore attachments like him tho.. :)
He makes a good point about list archives though... if the patch is inline,
you're left copying and pasting out of a web browser, which has all sorts of
formatting problems (like indentation, "<", etc).
If you send as an attachment (not gzipped, just plain text) then most mail
readers can read it inline *and* it will be saved in pristin form in the list
archives.
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/