From: Andreas Dilger <adilger@clusterfs.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Michael Hohnbaum <hohnbaum@us.ibm.com>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
Guillaume Boissiere <boissiere@adiglobal.com>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6] Most likely to be merged by Halloween... THE LIST]
Date: Fri, 19 Jul 2002 17:28:55 -0600 [thread overview]
Message-ID: <20020719232855.GH10315@clusterfs.com> (raw)
In-Reply-To: <3D388479.1060908@namesys.com>
On Jul 20, 2002 01:28 +0400, Hans Reiser wrote:
> Is Halloween the deadline for submission of patches, or the deadline for
> inclusion? If I send in reiser4 on Halloween day according to some
> timezone;-), have I made the deadline for inclusion into 2.6 even if it
> takes Linus a few months to reach my place in the queue of patches sent
> to him on Halloween day?
>
> I understand that earlier is better, and I will send it earlier if I
> can, but even if we do get the reiser4 core (that which does all that V3
> does but faster and on top of a plugin infrastructure) done before
> Halloween, we will inevitably add a few features and tweaks after doing
> the core, and we will want to send those in at the last minute.
Hans,
my understanding is that core changes that aren't in by Halloween are
not going to be accepted until 2.7. By pre-announcing the deadline,
it is hoped that people will have lots of time to submit things that are
ready for inclusion, as opposed to rushing to submit when the "freeze"
is announced all of a sudden.
If (as we all hope) the important features are added incrementally to
the development kernel over the next few months, maybe all of the usage
and testing that is going into the development kernel will not be
totally lost when the entire kernel is morphed under a huge weight of
patches.
It may even mean that there will not be an extra year of features (and
bugs) being added to the "frozen" kernel, and we will be able to start
2.7 earlier.
As always, I imagine that as long as you have any core changes in 2.5
before the freeze, it will not be impossible to add self-contained
things like filesystems and drivers after the freeze also.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-07-19 23:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D3875D4.3090102@us.ibm.com>
2002-07-19 20:40 ` [2.6] Most likely to be merged by Halloween... THE LIST] Michael Hohnbaum
2002-07-19 21:28 ` Hans Reiser
2002-07-19 23:28 ` Andreas Dilger [this message]
2002-07-19 23:37 ` Hans Reiser
2002-07-20 0:11 ` Rik van Riel
2002-07-20 0:31 ` Hans Reiser
2002-07-20 0:46 ` Rik van Riel
2002-07-20 0:53 ` Hans Reiser
2002-07-20 1:08 ` Rik van Riel
2002-07-20 1:55 ` Hans Reiser
2002-07-20 3:10 ` Oliver Xymoron
2002-07-20 5:03 ` Hans Reiser
2002-07-21 18:01 ` Marcin Dalecki
2002-07-30 14:43 ` Bill Davidsen
2002-07-30 14:46 ` Marcin Dalecki
2002-07-30 15:52 ` Hans Reiser
2002-07-20 0:13 ` Andreas Dilger
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=20020719232855.GH10315@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=boissiere@adiglobal.com \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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