From: Hans Reiser <reiser@namesys.com>
To: gmaxwell@gmail.com, Alexander Zarochentcev <zam@namesys.com>,
vs <vs@thebsh.namesys.com>, Andrew Morton <akpm@osdl.org>
Cc: thenewme91@gmail.com, Tom Vier <tmv@comcast.net>,
reiserfs-list@namesys.com
Subject: reiser4 merge status
Date: Wed, 07 Sep 2005 16:58:08 -0700 [thread overview]
Message-ID: <431F7E90.2050303@namesys.com> (raw)
In-Reply-To: <e692861c0509061948391f5cbe@mail.gmail.com>
Andrew, we have been working on a big patch that resolves the VFS
layering issues. This patch should be ready to send in any day now, we
are debugging it. We may not have been sending you a lot of emails, but
we have been working away at it. I don't understand why you think the
review feedback was lost.
I will have Zam review the email history, develop the bullet list for
you, and send it.
Hans
Gregory Maxwell wrote:
>Per Andrew Morton.
>
>reiser4 merge status:
> Stuck. Last time we discussed this I asked the reiser4 team to
> develop and negotiate a bullet-point list of things to be addressed.
> Once that's agreed to, implement it and then we can merge it. None of
> that has happened and as far as I know, all the review feedback which
> was provided was lost.
>
>:(
>
>
>
>
next prev parent reply other threads:[~2005-09-07 23:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 11:46 journal size reiserfs vs reiser4 Thomas Kuther
2005-09-01 12:48 ` Thomas Kuther
2005-09-01 12:53 ` Vladimir V. Saveliev
2005-09-01 13:03 ` PFC
2005-09-01 13:12 ` Thomas Kuther
2005-09-01 13:05 ` Thomas Kuther
2005-09-01 13:07 ` Peter Staubach
2005-09-01 13:37 ` Vladimir V. Saveliev
2005-09-01 15:25 ` Hans Reiser
2005-09-01 16:06 ` Peter Staubach
2005-09-01 16:23 ` Marcel Hilzinger
2005-09-01 17:03 ` David Masover
2005-09-01 17:27 ` Hans Reiser
2005-09-01 17:36 ` Peter Staubach
2005-09-01 17:59 ` Hans Reiser
2005-09-01 18:14 ` Peter Staubach
2005-09-01 22:17 ` Hans Reiser
2005-09-02 2:28 ` michael chang
2005-09-02 6:34 ` Vladimir V. Saveliev
2005-09-02 7:19 ` Hans Reiser
2005-09-02 7:39 ` PFC
2005-09-02 16:02 ` michael chang
2005-09-02 17:37 ` Łukasz Mierzwa
2005-09-02 18:08 ` Gregory Maxwell
2005-09-02 21:29 ` Matt Stegman
2005-09-04 1:04 ` michael chang
2005-09-04 2:38 ` David Masover
2005-09-04 3:48 ` Hans Reiser
2005-09-04 9:29 ` Clemens Eisserer
2005-09-04 16:42 ` David Masover
2005-09-05 12:16 ` michael chang
2005-09-05 18:20 ` David Masover
2005-09-05 21:24 ` michael chang
2005-09-06 13:59 ` Tom Vier
2005-09-06 20:32 ` michael chang
2005-09-06 20:45 ` David Masover
2005-09-06 20:47 ` michael chang
2005-09-06 21:03 ` David Masover
2005-09-06 23:10 ` Hans Reiser
2005-09-07 2:48 ` Gregory Maxwell
2005-09-07 23:58 ` Hans Reiser [this message]
2005-09-08 0:08 ` reiser4 merge status Andrew Morton
2005-09-06 20:36 ` journal size reiserfs vs reiser4 Gregory Maxwell
2005-09-06 20:41 ` michael chang
2005-09-07 14:01 ` Tom Vier
2005-09-07 20:18 ` michael chang
2005-09-05 12:14 ` michael chang
2005-09-03 10:08 ` Sander
2005-09-03 11:34 ` Pierre Etchemaïté
2005-09-04 0:15 ` Hans Reiser
2005-09-01 13:13 ` Marcel Hilzinger
2005-09-01 13:15 ` Thomas Kuther
2005-09-01 14:08 ` michael chang
2005-09-01 13:13 ` Lexington Luthor
2005-09-01 13:28 ` Thomas Kuther
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=431F7E90.2050303@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=gmaxwell@gmail.com \
--cc=reiserfs-list@namesys.com \
--cc=thenewme91@gmail.com \
--cc=tmv@comcast.net \
--cc=vs@thebsh.namesys.com \
--cc=zam@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.