public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <david@southpole.se>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [2.0.40-rc8] Works well
Date: Thu, 29 Jan 2004 00:50:43 +0100	[thread overview]
Message-ID: <20040128235043.GF16675@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0401290135070.29405-100000@midi>

On Thu, Jan 29, 2004 at 01:37:37AM +0200, Markus Hästbacka wrote:
> Btw - Are you going to announce the release of 2.0.40 (whenever it's
> coming) or just put it on kernel.org?

I will announce it.  It won't have any differences from 2.0.40-rc8
though (unless someone uncovers a flaw in -rc8 of course, which would
cause me to release an -rc9.)


Regards: David Weinehall
-- 
 /) David Weinehall <tao@acc.umu.se> /) Northern lights wander      (\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\)  http://www.acc.umu.se/~tao/    (/   Full colour fire           (/

  reply	other threads:[~2004-01-28 23:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 19:23 [PATCH 2.0.39] put_last_free() defined, but not used Coywolf Qi Hunt
2004-01-25 22:29 ` David Weinehall
2004-01-25 23:43   ` Jens Axboe
2004-01-26  2:01     ` David Weinehall
2004-01-27 17:10   ` [2.0.40-rc8] Works well Markus Hästbacka
2004-01-27 17:38     ` David Weinehall
2004-01-28  3:28     ` Coywolf Qi Hunt
2004-01-28  3:37       ` David Weinehall
2004-01-28  6:13         ` Markus Hästbacka
2004-01-28 15:17           ` David Weinehall
2004-01-28 23:37             ` Markus Hästbacka
2004-01-28 23:50               ` David Weinehall [this message]
2004-02-23  6:28         ` about 2.0 cleanup or adaption Coywolf Qi Hunt
2004-03-03 13:38         ` [PATCH 2.0.40] Fix comment error of prepare_binprm() in exec.c Coywolf Qi Hunt
2004-03-03 13:51           ` David Weinehall

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=20040128235043.GF16675@khan.acc.umu.se \
    --to=david@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midian@ihme.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