From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: trivial@kernel.org, Stefan Richter <stefanr@s5r6.in-berlin.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use a format string for linux_banner
Date: Sat, 28 Feb 2009 09:27:07 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0902280924150.3111@localhost.localdomain> (raw)
In-Reply-To: <20090228133602.GA28239@blimp.localdomain>
On Sat, 28 Feb 2009, Alex Riesen wrote:
> >
> > Please send patches as inline text or at least as plaintext attachment
> > in ascii encoding. linux/Documentation/email-clients.txt has help.
>
> Couldn't. Had to either choose the corporate firewal and gmail, or the
> Exchange-thing. Both will corrupt patches, unless send as attachment.
> Decided not to expose the corporate mail address.
Well, I _can_ tell you that I just ignore patches that I can't see
directly in my email reader. Others may pick them up, but for me it's an
issue of "ok, I can't easily even see the patch, and the person didn't
bother to do it right - it's not worth my time".
What people _can_ do is to send it both as a crazy attachment _and_ as
plaintext. If they plaintext gets corrupted, the attachment still works,
and the plaintext is at least somethign I can see and thus in my mail
reader decide whether it's worth my time to save the attachment and look
at it outside the mail reader.
Linus
next prev parent reply other threads:[~2009-02-28 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 9:04 [PATCH] Use a format string for linux_banner Alex Riesen
2009-02-28 12:01 ` Stefan Richter
2009-02-28 13:36 ` Alex Riesen, Alex Riesen
2009-02-28 17:27 ` Linus Torvalds [this message]
2009-05-24 13:30 ` [PATCH] Use a format " Alex Riesen
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=alpine.LFD.2.00.0902280924150.3111@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=trivial@kernel.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