public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: linux-2.6.12
Date: Wed, 22 Jun 2005 08:22:20 -0700	[thread overview]
Message-ID: <pan.2005.06.22.15.22.19.81677@cox.net> (raw)
In-Reply-To: pan.2005.06.18.14.20.56.170191@cox.net

Duncan posted <pan.2005.06.18.14.20.56.170191@cox.net>, excerpted below,
on Sat, 18 Jun 2005 07:20:56 -0700:

> I have no reason to believe reiser4 will be added in the next couple
> releases, either, so 2.6.15 or later I'd guess, tho I have no exclusive
> info on it to cause me to think that.

Things change.  LWN is reporting on Andrew's "Looking forward to 2.6.13"
post to LKML.  From the context, it appears not everything mentioned as
mergeable will be in 2.6.13, but some will be, with others showing up
later.  He is saying, however, that there's nothing serious holding items
he considers mergable up, so they'll be merged sooner rather than later,
whether "sooner" == .13 or .14 or whatever, more likely than .20, in any
case.

Reiser4 is considered mergeable, but with some caveats that might mean
post .13, still, it now looks to be .14 or .15-ish, rather than .20-ish,
provided egos don't get too far in the way, always a possibility with Hans
Reiser, it seems, unfortunately.

There are some other patches mentioned of significance, including
swsusp_SMP, which I've personally been waiting for, but I'll refrain from
mentioning any more, and just point to the LWN article with the whole list
and comments, plus references to the archive thread for more details.

http://lwn.net/Articles/140773/

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-06-22 15:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18  4:22 [gentoo-dev] linux-2.6.12 Andrew Muraco
2005-06-18  4:50 ` Mike Frysinger
2005-06-18  4:52   ` Andrew Muraco
2005-06-18  5:05     ` Jason Wever
2005-06-18  6:03       ` Kumba
2005-06-18  6:04         ` Andrew Muraco
2005-06-18  6:26           ` Kumba
2005-06-18 10:27             ` Luca Barbato
2005-06-18 10:44               ` Jason Stubbs
2005-06-18 13:34               ` Omkhar Arasaratnam
2005-06-18 14:20                 ` [gentoo-dev] linux-2.6.12 Duncan
2005-06-22 15:22                   ` Duncan [this message]
2005-06-18 16:44                 ` [gentoo-dev] linux-2.6.12 Daniel Drake
2005-06-18 20:47                   ` Andrew Muraco
2005-06-19 23:12                   ` Omkhar Arasaratnam
2005-06-20 17:00                     ` Daniel Drake
2005-06-20 15:44                 ` Chris Gianelloni
2005-06-18  5:05     ` Jason Stubbs
2005-06-18  5:53       ` Andrew Muraco
2005-06-18  6:03         ` Mike Frysinger
2005-06-18  6:21           ` Andrew Muraco
2005-06-18  6:28             ` Mike Frysinger
2005-06-18  6:31               ` Andrew Muraco
2005-06-18 15:04                 ` Chris PeBenito
2005-06-18  7:54             ` Daniel Drake
2005-06-18 13:28 ` Omkhar Arasaratnam

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=pan.2005.06.22.15.22.19.81677@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.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