From: Ralf Baechle <ralf@linux-mips.org>
To: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>
Cc: Jan Pedersen <jan.pedersen@glaze.dk>, linux-mips@linux-mips.org
Subject: Re: support for NS DP83847
Date: Fri, 30 Sep 2005 23:46:08 +0100 [thread overview]
Message-ID: <20050930224608.GB14463@linux-mips.org> (raw)
In-Reply-To: <43307CA9.1070506@total-knowledge.com>
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 parent reply other threads:[~2005-10-03 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 21:12 support for NS DP83847 Jan Pedersen
2005-09-20 21:12 ` Jan Pedersen
2005-09-20 21:18 ` Ilya A. Volynets-Evenbakh
2005-09-20 21:27 ` Jan Pedersen
2005-09-20 21:27 ` Jan Pedersen
2005-09-30 22:49 ` Ralf Baechle
2005-09-30 22:46 ` Ralf Baechle [this message]
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=20050930224608.GB14463@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ilya@total-knowledge.com \
--cc=jan.pedersen@glaze.dk \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.