linux-mips
[Top] [All Lists]

Re: support for NS DP83847

To: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>
Subject: Re: support for NS DP83847
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 30 Sep 2005 23:46:08 +0100
Cc: Jan Pedersen <jan.pedersen@glaze.dk>, linux-mips@linux-mips.org
In-reply-to: <43307CA9.1070506@total-knowledge.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050920211245.730CF376471@rocket.glaze.se> <43307CA9.1070506@total-knowledge.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
On Tue, Sep 20, 2005 at 02:18:33PM -0700, Ilya A. Volynets-Evenbakh wrote:

> If you are interested in any patches being accepted into LMO CVS tree,
> you should email patches in question, not URLs. Noone will bother looking
> up your stuff on the web.

Or simply see Documentation/SubmittingPatches:

[...]
6) No MIME, no links, no compression, no attachments.  Just plain text.

Linus and other kernel developers need to be able to read and comment
on the changes you are submitting.  It is important for a kernel
developer to be able to "quote" your changes, using standard e-mail
tools, so that they may comment on specific portions of your code.

For this reason, all patches should be submitting e-mail "inline".
WARNING:  Be wary of your editor's word-wrap corrupting your patch,
if you choose to cut-n-paste your patch.

Do not attach the patch as a MIME attachment, compressed or not.
Many popular e-mail applications will not always transmit a MIME
attachment as plain text, making it impossible to comment on your
code.  A MIME attachment also takes Linus a bit more time to process,
decreasing the likelihood of your MIME-attached change being accepted.

Exception:  If your mailer is mangling patches then someone may ask
you to re-send them using MIME.
[...]

I'm doing plenty of the MIPS maintenance work offline, so URLs really
don't fly.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>