From: "Michael J. Cohen" <mjc@325i.org>
To: Sean Reifschneider <jafo@tummy.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6 Kernel Pool Results
Date: Fri, 19 Dec 2003 14:30:18 -0500 [thread overview]
Message-ID: <3FE351CA.3010902@325i.org> (raw)
In-Reply-To: <20031219190903.GA28010@tummy.com>
Sean Reifschneider wrote:
>teve Ratcliffe, Master Software Project Estimator, has most correctly
>estimated the release of the Linux version 2.6 kernel. On January 6,
>2001 (within 4 hours of when the 2.6 kernel pool was opened), he entered
>a guess which was accurate within 15 hours. Check the results for some
>interesting statistics and submit your guess for the 2.8 pool.
>
> http://kernelpool.tummy.com/kernelpool/results.html
> http://kernelpool.tummy.com/kernelpool/
>
>Sean
>
>(A friend who's a subscriber suggested I send the announcement to LKML.
>I'm not on it, so copy me if you reply and want a response from me. :-)
>
>
Neat, I'll have to submit a prediction. :)
Michael
prev parent reply other threads:[~2003-12-19 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 19:09 Linux 2.6 Kernel Pool Results Sean Reifschneider
2003-12-19 19:30 ` Michael J. Cohen [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=3FE351CA.3010902@325i.org \
--to=mjc@325i.org \
--cc=jafo@tummy.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