From: Tom Rini <trini@kernel•crashing.org>
To: Dave Wolfe <dwolfe@lists•linuxppc.org>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Correct way to submit a patch?
Date: Tue, 5 Feb 2002 09:18:52 -0700 [thread overview]
Message-ID: <20020205161852.GL32707@opus.bloom.county> (raw)
In-Reply-To: <20020204142503.A20449@lists.linuxppc.org>
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.. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 16:18 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 [this message]
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=20020205161852.GL32707@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=dwolfe@lists$(echo .)linuxppc.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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