From: Hans Reiser <reiser@namesys.com>
To: Chris Shoemaker <c.shoemaker@cox.net>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: List of things requested by lkml for reiser4 inclusion (to review)
Date: Fri, 09 Sep 2005 13:42:19 -0700 [thread overview]
Message-ID: <4321F3AB.4070701@namesys.com> (raw)
In-Reply-To: <20050909175739.GA32503@pe.Belkin>
Chris Shoemaker wrote:
>On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
>
>
>>If we lose every remaining point of this list, we can generate a patch
>>in a few days, because the VFS work was the only substantive (in coding
>>hours) task, and it is done. Do I remember right that the submission
>>deadline is a week from Monday for 2.6.14 inclusion?
>>
>>
>
>No. 14 days from release date of 2.6.13, which was 8/29, so deadline
>is 9/12, this coming Monday.
>
>-chris
>
>
>
>
IIRC, Linus announced that since he was going on vacation for 7 days,
this release only it would be 3 weeks, so it is a week from Monday that
we must submit by, yes?
Hans
next prev parent reply other threads:[~2005-09-09 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509091817.39726.zam@namesys.com>
2005-09-09 17:36 ` List of things requested by lkml for reiser4 inclusion (to review) Hans Reiser
2005-09-09 17:57 ` Chris Shoemaker
2005-09-09 20:42 ` Hans Reiser [this message]
2005-09-09 20:48 ` Nish Aravamudan
2005-09-09 20:49 ` Randy.Dunlap
2005-09-09 20:57 ` Chris Shoemaker
2005-09-09 18:57 ` Christoph Hellwig
2005-09-09 19:00 ` Christoph Hellwig
2005-09-09 21:21 ` Hans Reiser
2005-09-10 4:51 ` Kyle Moffett
2005-09-10 7:28 ` Paul Jackson
2005-09-09 21:41 ` Andrew Morton
2005-09-09 22:02 ` Hans Reiser
2005-09-12 18:08 ` Hans Reiser
2005-09-12 19:40 ` Horst von Brand
2005-09-10 10:14 ` Pekka Enberg
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=4321F3AB.4070701@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=akpm@osdl.org \
--cc=c.shoemaker@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@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 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.