From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ARGH! (Is there an HTML archive for linux-kernel that patches work from?)
Date: Sun, 27 Oct 2002 23:34:42 -0500 [thread overview]
Message-ID: <200210280434.g9S4Ygh13812@marc2.theaimsgroup.com> (raw)
On 2002-10-27, Rob Landley <landley@trommello.org> wrote:
> Marc.theaimsgroup.com has a lovely "raw mode", but it truncates posts
> that are too long.
This is true, and I consider it a bug. However the limit should be quite
high--either 256KB or 1MB or so. So raising / eliminating the limit isn't
high on my priority list :-P Please do let us know (me directly, or
webguy@theaimsgroup.com) if you find other mails that have been truncated
at shorter than this, I'll look into it.
Also, I'm interested in any corner cases where the attachment-parser messes
up--most of all when it fails to make attachments properly downloadable,
but also, to a lesser extent, any predictably readable mime-type, encoding,
etc which it currently doesn't try to print in-line, but could.
> Erich: Could you put your october 25 numa scheduler posting on your
> home page somewhere? I tried:
> http://home.arcor.de/efocht/patches/01-numa_sched_core-2.5.44-10a.patch
If I've got the right mail, you're after this one, correct?
http://marc.theaimsgroup.com/?l=linux-kernel&m=103556765829589&w=2
...Which looks complete from here? That particular patch can be downloaded
directly as:
http://marc.theaimsgroup.com/?l=linux-kernel&m=103556765829589&q=p3
Thanks,
Hank Leininger <hlein@progressive-comp.com>
next reply other threads:[~2002-10-28 4:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 4:34 Hank Leininger [this message]
2002-10-30 21:54 ` [OT] " hlein
[not found] <200210271945.20084.landley@trommello.org>
2002-10-28 7:49 ` hlein
-- strict thread matches above, loose matches on Subject: below --
2002-10-27 16:01 Rob Landley
2002-10-28 0:08 ` Erich Focht
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=200210280434.g9S4Ygh13812@marc2.theaimsgroup.com \
--to=linux-kernel@progressive-comp.com \
--cc=hlein@progressive-comp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®