mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
To: "Adrian Bunk" <bunk@stusta.de>,
	"Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Outlook Sux (Was: [2.6 patch] dpt_i2o fix for deadlock condition)
Date: Tue, 29 Nov 2005 14:30:09 -0500	[thread overview]
Message-ID: <547AF3BD0F3F0B4CBDC379BAC7E4189F01E3DE12@otce2k03.adaptec.com> (raw)

From: Adrian Bunk [mailto:bunk@stusta.de] writes: 
>> There must still be a way to tell outlook to make the type something 
>> useful, rather than application/octet-stream.  maybe if the extension

>> was .patch.txt it would do something smarter.
> Patches in Attachments aren't nice, but better than corrupted patches.

:-)

Part of the problem is cut-n-paste engines on M$ and preservation of
content, the other part of the problem is the MUA making up it's own
rules on what constitutes a text document. It is not the MTA, sendmail
is blameless.

> It's unfortunate, but bitching on the people who are somehow forced to

> use crappy email clients is IMHO not a good idea.

We could always require that if a patch is done as an attachment, that
if it is smaller than 2K and/or at the submitters option, it also be
present as in-line content for code review convenience?

Thanks for that defense, I appreciate it. I am trapped in corporate
policy and MIS monitoring requirements. I have tried to make our MIS
department miserable over this issue, the sheer quantity of attempts to
mitigate is boggling and is still open. If I was paranoid, I'd almost
believe that M$ specifically decided to ignore RFC822 and all it's
children just to make it an impossible tool to use for submitting Linux
patches.

Now, if *someone* had an idea how I could configure Outlook 2002 to
properly produce in-line patches *that* would earn my eternal gratitude
(or a single stay at Hotel Salyzyn when visiting the Orlando Mouse House
;-> ). Outlook 2003 gets worse still by corrupting attachments (!) and I
thus reverted back to 2002.

Sincerely -- Mark Salyzyn

             reply	other threads:[~2005-11-29 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 19:30 Salyzyn, Mark [this message]
2005-11-29 19:52 ` Jesper Juhl

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=547AF3BD0F3F0B4CBDC379BAC7E4189F01E3DE12@otce2k03.adaptec.com \
    --to=mark_salyzyn@adaptec.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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

all inboxes | Powered by JetHome®