From: Jarek Poplawski <jarkao2@o2.pl>
To: Randy Dunlap <rdunlap@xenotime.net>,
Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx
Date: Fri, 6 Oct 2006 08:57:22 +0200 [thread overview]
Message-ID: <20061006065722.GA2084@ff.dom.local> (raw)
In-Reply-To: <20061006055732.GA1743@ff.dom.local>
On Fri, Oct 06, 2006 at 07:57:32AM +0200, Jarek Poplawski wrote:
> On Thu, Oct 05, 2006 at 01:52:19PM -0700, Randy Dunlap wrote:
...
> > see http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
...
dangerous feature of Thunderbird - you never could be sure
> how a message will look because it is reformated
> after send command. So it isn't "you send what you see"
> definitely (I mean text messages here).
I see from this link it was told in the discussion,
so I'll only add that with a feature like this even
if you do everything correctly you are never sure.
You always have to trust yourself you didn't miss
any step.
Jarek P.
prev parent reply other threads:[~2006-10-06 6:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 1:47 [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx Larry Finger
[not found] ` <45021D4A.6040805-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 15:23 ` John W. Linville
2006-09-09 16:04 ` Larry Finger
[not found] ` <4502E62B.5060601-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 19:42 ` Daniel Drake
2006-09-11 19:28 ` John W. Linville
2006-09-11 19:59 ` Larry Finger
[not found] ` <4505C005.2070302-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-11 20:35 ` John W. Linville
2006-09-11 22:04 ` Jeff Garzik
2006-09-14 8:25 ` Jarek Poplawski
2006-09-14 8:29 ` Jarek Poplawski
2006-10-05 20:52 ` Randy Dunlap
2006-10-06 5:57 ` Jarek Poplawski
2006-10-06 6:19 ` Jarek Poplawski
2006-10-06 6:57 ` Jarek Poplawski [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=20061006065722.GA2084@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.