From: hollis@austin.ibm.com
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Correct way to submit a patch?
Date: Tue, 5 Feb 2002 10:25:13 -0600 [thread overview]
Message-ID: <20020205162511.GN510@austin.ibm.com> (raw)
In-Reply-To: <20020205161852.GL32707@opus.bloom.county>
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:
> >
> > [ 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.
>
> 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/
next prev parent reply other threads:[~2002-02-05 16: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
2002-02-05 16:18 ` Tom Rini
2002-02-05 16:25 ` hollis [this message]
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=20020205162511.GN510@austin.ibm.com \
--to=hollis@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).