From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ troubles, processor overload
Date: Tue, 22 Jun 2004 16:26:23 +0000 [thread overview]
Message-ID: <40D85DAF.3030205@wildgooses.com> (raw)
In-Reply-To: <01eb01c457f0$5e00e120$903113d8@uranus>
Adam Towarnyckyj wrote:
>I'd love to share. Whoever was interested in that, please let me know in
>an email. Thanks for the suggestions. I really appreciate them and I'll
>look into it.
>
>
>
Well, I would for one. However, it looks like Ralph perhaps only wants
a simple solution, so perhaps he isn't interested?
Why not pop the stuff on a web page and send us a link?
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-22 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 0:32 [LARTC] CBQ troubles, processor overload Adam Towarnyckyj
2004-06-22 7:09 ` Ed Wildgoose
2004-06-22 16:10 ` Adam Towarnyckyj
2004-06-22 16:26 ` Ed Wildgoose [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=40D85DAF.3030205@wildgooses.com \
--to=lists@wildgooses.com \
--cc=lartc@vger.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