From: Michael Buesch <mbuesch@freenet.de>
To: kernel@kolivas.org
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Staircase scheduler v7.4
Date: Sat, 26 Jun 2004 18:33:29 +0200 [thread overview]
Message-ID: <200406261833.52060.mbuesch@freenet.de> (raw)
In-Reply-To: <1088212304.40dccd5035660@vds.kolivas.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 26 June 2004 03:11, you wrote:
> There was the one clear bug that Adrian Drzewiecki found (thanks!) that is easy
> to fix. Can you see if this has any effect before I go searching elsewhere?
Ok, I'll try it.
OT:
Some mails bounce on kernel@kolivas.org:
This is the Postfix program at host bhhdoa.org.au.
####################################################################
# THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. #
####################################################################
Your message could not be delivered for 4.0 hours.
It will be retried until it is 5.0 days old.
For further assistance, please send mail to <postmaster>
The Postfix program
<kernel@kolivas.org>: connect to kolivas.org[211.28.147.198]: Connection timed
out
Final-Recipient: rfc822; kernel@kolivas.org
Action: delayed
Status: 4.0.0
Diagnostic-Code: X-Postfix; connect to kolivas.org[211.28.147.198]: Connection
timed out
Will-Retry-Until: Wed, 30 Jun 2004 13:29:45 -0400 (EDT)
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA3aVtFGK1OIvVOP4RApVwAJ9ows81hLZoQtiFer5/F9DDZwKrHACdF/Cs
y1sfWD8BusvvLWJMJbcT+yY=
=Kd+H
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-26 16:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 16:40 [PATCH] Staircase scheduler v7.4 Michael Buesch
2004-06-25 16:46 ` Con Kolivas
2004-06-25 18:44 ` Michael Buesch
2004-06-25 19:05 ` Willy Tarreau
2004-06-25 19:48 ` Michael Buesch
2004-06-26 1:11 ` kernel
2004-06-26 16:33 ` Michael Buesch [this message]
2004-06-26 17:29 ` Michael Buesch
2004-06-27 9:14 ` Con Kolivas
2004-06-27 19:17 ` Felipe Alfaro Solana
2004-06-27 19:28 ` Michael Buesch
2004-06-27 21:55 ` Felipe Alfaro Solana
2004-06-28 0:15 ` Con Kolivas
2004-06-28 8:40 ` Felipe Alfaro Solana
2004-06-28 8:49 ` Nick Piggin
2004-06-28 11:53 ` Felipe Alfaro Solana
2004-06-28 12:11 ` Con Kolivas
2004-06-28 15:03 ` Oswald Buddenhagen
2004-06-28 15:19 ` Con Kolivas
2004-06-28 15:39 ` Oswald Buddenhagen
2004-06-28 17:11 ` Felipe Alfaro Solana
2004-06-29 4:36 ` Nick Piggin
2004-06-28 23:21 ` Peter Williams
2004-06-29 4:44 ` Nick Piggin
2004-06-29 6:01 ` Ed Sweetman
2004-06-29 6:55 ` Nick Piggin
2004-06-26 2:05 ` Con Kolivas
2004-06-27 10:24 ` Con Kolivas
2004-06-27 10:27 ` Con Kolivas
2004-06-27 23:50 ` Peter Williams
2004-06-27 12:00 ` Con Kolivas
2004-06-27 12:04 ` Con Kolivas
2004-06-27 12:54 ` Michael Buesch
2004-06-27 13:15 ` Con Kolivas
2004-06-25 16:46 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2004-06-25 14:38 Con Kolivas
2004-06-25 18:32 ` Matthias Urlichs
2004-06-26 1:28 ` Con Kolivas
2004-06-25 22:20 ` Willy Tarreau
2004-06-26 1:05 ` kernel
2004-06-26 20:04 ` Wes Janzen
2004-06-26 20:11 ` Michael Buesch
2004-06-26 21:14 ` Wes Janzen
2004-06-26 21:38 ` Prakash K. Cheemplavam
2004-06-27 9:16 ` Con Kolivas
2004-06-27 11:40 ` Grzegorz Kulewski
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=200406261833.52060.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=kernel@kolivas.org \
--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 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.