From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 5 Feb 2002 11:23:30 -0600 From: Dave Wolfe To: Tom Rini Cc: linuxppc-dev@lists.linuxppc.org Subject: Re: Correct way to submit a patch? Message-ID: <20020205112330.A28293@lists.linuxppc.org> References: <3C5E3B8F.5060105@elsoft.ch> <20020204004850.24542@mailhost.mipsys.com> <20020204142503.A20449@lists.linuxppc.org> <20020205161852.GL32707@opus.bloom.county> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20020205161852.GL32707@opus.bloom.county>; from trini@kernel.crashing.org on Tue, Feb 05, 2002 at 09:18:52AM -0700 Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: [ Tom Rini writes: ] > 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.. :) Then you risk mangled patches, and I guarantee that patches in the archives will be unusable since they're converted to HTML. I'm not fond of attachments either, but this is one application of them that is appropriate. -- Dave Wolfe ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/