From: David Masover <ninja@slaphack.com>
To: Pysiak Satriani <pysiak.satriani@wp.pl>
Cc: reiserfs-list@namesys.com
Subject: Re: r4.1 ?
Date: Tue, 25 Jan 2005 17:54:33 -0600 [thread overview]
Message-ID: <41F6DC39.6000705@slaphack.com> (raw)
In-Reply-To: <27547285.20050125224458@wp.pl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pysiak Satriani wrote:
| Hi,
|
| I was wondering how close are we to reiser4.1 ?
| Like in % of work done or some other measure.
|
| http://www.namesys.com mentions r4.1
|
| 'this and that' will be included in r4.1
Which means it would either be included in some sort of experimental
form of r4, or (more likely, I think) in a new branch.
I haven't seen any work on any of the things delayed for 4.1, meaning
either we are 0% done, or Hans has moved to a cathedral style of
development.
That, or I just haven't noticed such work. I don't often read source code.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQfbcOHgHNmZLgCUhAQIt5A//V477ZEMTobpz4II7I3gIzEzlzqScWkhF
O09kFgT1RLhFsQbZnlEr3H7pMBG5IopN7u67rY3bAtrmiP+OuQg6viBuywVRCHKV
/olNDpnxmdKv1eCuqIvmWWdwg6HVxuZ/jy5owwUuU22n0PRu7X+EkfHex92hJ6zQ
cZLjq4Xe2MuH6Y7lF7z8Low3vn74tZYmVp8iLgTNeSuRRt94knPiIGJvVEIawKbU
i6oFdeB63pXHwQUPul5AEs5hn6+yOyIln/DdSmO4FeWIMXA8BX8+E8tz2VYJ2AoG
IPk13BCKpiPdKU0FBiK3Bre3908Gdu4laI0LnLIdJ9uTQry06ctvl061EebCopJO
130KIyao9BVMnc7rmO/h0Qu4bCGxkU5tq5kzeXkBSAvi8FUQ6Rs6FJ0aR7jPMMUi
LiLrz2T8qmI1JsIQEIocOu9waWYGe+CK5nLLDbi6933u8dcKGsWNi4umxNURxV/m
WLePoIRQN8ImJT6/K4mog+99cjOARbdq4lXQfNV/FRaTRZT/53EFgn7OKabcRcde
ifW04kzCy5kX8SnJhovxggR8DHqBMZz0Uq5s1/c49n4sVeIqAkMaK9rBeWuvUn/C
makUvW8Lq7/pKVa2rhZQNycVFThHmwbWFmuR4yIBJmxo8XjyoPtNlCE3OdGx1OYR
nNAr7J676gk=
=no6b
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-01-25 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 21:44 r4.1 ? Pysiak Satriani
2005-01-25 23:54 ` David Masover [this message]
2005-01-26 17:44 ` Hans Reiser
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=41F6DC39.6000705@slaphack.com \
--to=ninja@slaphack.com \
--cc=pysiak.satriani@wp.pl \
--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.