From: Christian Axelsson <smiler@lanil.mine.nu>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11-mm1
Date: Wed, 17 Dec 2003 12:11:49 +0100 [thread overview]
Message-ID: <3FE039F5.5030703@lanil.mine.nu> (raw)
In-Reply-To: <200312171037.16969.andrew@walrond.org>
Andrew Walrond wrote:
> On Wednesday 17 Dec 2003 9:43 am, Andrew Morton wrote:
> What are your intentions with -mm when you take over 2.6? Is any of -mm
> getting into 2.6 before 2.6.0 release? Is it mainly queued for 2.6.1?
I would like to know aswell :)
Will you be "bleeding edge" maintainer aswell or will that be handed
over to someone else?
--
Christan Axelsson
smiler@lanil.mine.nu
next prev parent reply other threads:[~2003-12-17 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 9:43 2.6.0-test11-mm1 Andrew Morton
2003-12-17 10:13 ` Question about UFS/UFS2 Niraj Kumar
2003-12-17 10:37 ` 2.6.0-test11-mm1 Andrew Walrond
2003-12-17 11:11 ` Christian Axelsson [this message]
2003-12-17 11:51 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-18 3:24 ` 2.6.0-test11-mm1 Thomas Molina
2003-12-18 3:36 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-19 18:21 ` 2.6.0-test11-mm1 Jens Axboe
2003-12-17 11:52 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-17 13:30 ` 2.6.0-test11-mm1 Felipe Alfaro Solana
2003-12-17 11:57 ` UP build broken (Re: 2.6.0-test11-mm1) Dagfinn Ilmari Mannsåker
2003-12-17 11:55 ` Luiz Fernando Capitulino
2003-12-17 13:56 ` 2.6.0-test11-mm1 Zwane Mwaikambo
2003-12-17 18:22 ` 2.6.0-test11-mm1 Diego Calleja García
2003-12-17 22:01 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-17 23:59 ` 2.6.0-test11-mm1 Paul Mackerras
2003-12-19 16:58 ` [patch] 2.6.0-test11-mm1: isdn/eicon/eicon_mod.c doesn't compile Adrian Bunk
2003-12-26 18:22 ` SUCCESS Re: 2.6.0-test11-mm1 Matthias Urlichs
2003-12-26 19:15 ` Linus Torvalds
2003-12-28 21:59 ` Matthias Urlichs
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=3FE039F5.5030703@lanil.mine.nu \
--to=smiler@lanil.mine.nu \
--cc=andrew@walrond.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox