From: Andreas Dilger <adilger@clusterfs.com>
To: Rob Landley <landley@trommello.org>
Cc: karim@opersys.com, linux-kernel@vger.kernel.org, boissiere@nl.linux.org
Subject: Re: Crunch time -- Final merge candidates for 3.0 (the list).
Date: Mon, 21 Oct 2002 02:05:17 -0600 [thread overview]
Message-ID: <20021021080517.GB17430@clusterfs.com> (raw)
In-Reply-To: <200210202147.23712.landley@trommello.org>
On Oct 20, 2002 21:47 -0500, Rob Landley wrote:
> On Monday 21 October 2002 01:43, Andreas Dilger wrote:
> > On Oct 20, 2002 20:37 -0500, Rob Landley wrote:
> > > Ted Tso has also been posting new ext2/ext3 code with extended attributes
> > > and access control lists.
> > >
> > > So, 11 items from the 2.5 status list (in -aa, in -mm, and "ready"), plus
> > > kexec, kernelconfig, and ACL for EXT3. I believe this brings the total
> > > number of pending patchsets still hoping for 2.5 inclusion to 14.
> >
> > I belive that the ext3 EA+ACL stuff is now in -mm.
>
> Query: is the stuff in -mm guaranteed to make it into Linus's tree? Or is it
> another variant of -ac and -dj, from which Linus pulls what he wants?
I doubt it. However, being included in "-mm" or "-ac" is one step closer to
being included in "" than just being a random patch/cset on the internet...
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-10-21 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 23:49 Crunch time -- Final merge candidates for 3.0 (the list) Rob Landley
2002-10-21 5:44 ` Hans Reiser
2002-10-21 6:03 ` Karim Yaghmour
2002-10-21 1:37 ` Rob Landley
2002-10-21 6:43 ` Andreas Dilger
2002-10-21 2:47 ` Rob Landley
2002-10-21 8:05 ` Andreas Dilger [this message]
2002-10-21 8:25 ` Andrew Morton
2002-10-21 11:56 ` Alan Cox
2002-10-21 12:23 ` Denis Vlasenko
2002-10-21 3:00 ` Rob Landley
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=20021021080517.GB17430@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=boissiere@nl.linux.org \
--cc=karim@opersys.com \
--cc=landley@trommello.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.