From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Hans Reiser <reiser@bitshadow.namesys.com>,
David Masover <jedi@ninja.dynup.net>,
reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 errors
Date: Tue, 16 Dec 2003 15:30:29 +0300 [thread overview]
Message-ID: <3FDEFAE5.4090500@namesys.com> (raw)
In-Reply-To: <200312161411.36067.vitaly@namesys.com>
Vitaly Fertman wrote:
>On Tuesday 16 December 2003 06:28, Hans Reiser wrote:
>
>
>>On Tuesday 16 December 2003 06:10, David Masover wrote:
>>
>>
>>>Vitaly Fertman wrote:
>>>
>>>
>>>>...
>>>>
>>>>hm, this is strange. what reiser4progs do you use?
>>>>there are a lot of fixes have been made recently, I will send
>>>>you the uptodate code in the next email, you should try it first.
>>>>
>>>>
>>>I have the latest from the website, as of November 11, I think.
>>>
>>>
>>Sounds like Vitaly needs to release a new snapshot. Nikita, aren't we
>>overdue for a new snapshot for the kernel code also?
>>
>>
>
>right, but I still have a pair of not fixed bugs. and Yura has some also.
>debugging...
>
>
>
Ok, then let us try for next Monday, if the code is ready by then.
--
Hans
next prev parent reply other threads:[~2003-12-16 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 18:02 fsck.reiser4 errors Jedi Ninja
2003-12-15 13:35 ` Vitaly Fertman
2003-12-16 3:10 ` David Masover
2003-12-16 3:28 ` Hans Reiser
2003-12-16 8:23 ` Nikita Danilov
2003-12-16 11:13 ` Vitaly Fertman
2003-12-16 12:30 ` Hans Reiser [this message]
[not found] ` <200312151657.58459.vitaly@namesys.com>
2003-12-20 17:24 ` Jedi Ninja
2003-12-22 12:08 ` Vitaly Fertman
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 23:41 Bob Vincent
2004-02-25 12:31 ` Vitaly Fertman
2004-02-25 13:35 ` Hans Reiser
2004-02-25 14:42 ` Vitaly Fertman
2004-02-25 19:01 ` Hans Reiser
2004-02-25 21:53 ` Vitaly Fertman
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=3FDEFAE5.4090500@namesys.com \
--to=reiser@namesys.com \
--cc=jedi@ninja.dynup.net \
--cc=reiser@bitshadow.namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.