From: "David S. Miller" <davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: miles@megapathdsl.net, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: What is standing in the way of opening the 2.5 tree?
Date: Sat, 27 Oct 2001 22:46:02 -0700 (PDT) [thread overview]
Message-ID: <20011027.224602.74750641.davem@redhat.com> (raw)
In-Reply-To: <3BDB91D7.C7975C44@mandrakesoft.com>
In-Reply-To: <1004219488.11749.19.camel@stomata.megapathdsl.net> <3BDB91D7.C7975C44@mandrakesoft.com>
From: Jeff Garzik <jgarzik@mandrakesoft.com>
Date: Sun, 28 Oct 2001 01:04:23 -0400
Most likely we are
(a) waiting for stuff to get merged from Alan's tree, and
For the record, I do not feel comfortable at all with forking
2.4.x over to Alan until all of the non-trivial bits of the
AC patches are merged into Linus's tree.
In particular, the quota stuff, which has sat in Alan's tree forever.
If Linus is ignoring the changes it probably is for a good reason
but it would be nice for him to let Alan know what that reason is :-)
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-28 5:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-27 21:51 What is standing in the way of opening the 2.5 tree? Miles Lane
2001-10-28 5:04 ` Jeff Garzik
2001-10-28 5:46 ` David S. Miller [this message]
2001-10-29 1:58 ` Andreas Dilger
2001-10-30 5:09 ` What is standing in the way of opening the 2.5 tree? (quotas?) Neil Brown
2001-10-30 18:29 ` What is standing in the way of opening the 2.5 tree? Jan Kara
2001-10-30 23:03 ` Alan Cox
2001-10-31 13:19 ` Jan Kara
2001-10-28 11:28 ` Allan Sandfeld
-- strict thread matches above, loose matches on Subject: below --
2001-10-30 21:11 Thomas Hood
2001-10-30 21:39 ` lost
2001-10-30 21:59 ` Sujal Shah
2001-10-31 19:18 ` Michael Peddemors
2001-10-31 19:39 ` David Lang
2001-10-30 22:44 ` Alan Cox
2001-10-31 1:36 ` Mike Fedyk
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=20011027.224602.74750641.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
--cc=torvalds@transmeta.com \
/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