From: Steven Cole <elenstev@mesatop.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 3Com 3cr990 driver release
Date: 14 Feb 2003 16:01:01 -0700 [thread overview]
Message-ID: <1045263664.4920.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1045243705.1353.30.camel@irongate.swansea.linux.org.uk>
On Fri, 2003-02-14 at 10:28, Alan Cox wrote:
> On Fri, 2003-02-14 at 16:09, Larry McVoy wrote:
> > Sure you can, unless your objection extends to getting at data which is in
> > BK over the web. http://typhoon.bkbits.net:8080/typhoon-2.4/patch@+
> >
>
> Patch isnt noted for its handling of pretty blue html btw
>
Larry,
A possible solution to this is to provide the equivalent of the
"Download Message Raw" link which marc.theaimsgroup.com provides, e.g.
here: http://marc.theaimsgroup.com/?l=linux-net&m=104524036019392&q=raw
BTW, thanks for creating and providing BK. It seems to me that the
positive contributions you've made far out-weigh the negative aspects
which some perceive.
Steven
next prev parent reply other threads:[~2003-02-14 22:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 7:50 3Com 3cr990 driver release David Dillow
2003-02-14 8:20 ` Jeff Garzik
2003-02-14 14:33 ` Alan Cox
2003-02-14 15:19 ` Larry McVoy
2003-02-14 16:54 ` Alan Cox
2003-02-14 16:09 ` Larry McVoy
2003-02-14 17:23 ` Alan Cox
2003-02-14 16:36 ` Larry McVoy
2003-02-14 17:04 ` Tomas Szepe
2003-02-14 17:12 ` Larry McVoy
2003-02-14 18:40 ` Roman Zippel
2003-02-14 18:44 ` Larry McVoy
2003-02-14 18:59 ` Roman Zippel
2003-02-15 11:34 ` Henning P. Schmiedehausen
2003-02-14 17:28 ` Alan Cox
2003-02-14 23:01 ` Steven Cole [this message]
2003-02-14 17:20 ` David Dillow
2003-02-14 20:52 ` Alan Cox
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=1045263664.4920.14.camel@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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