All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
	ReiserFS List <reiserfs-list@namesys.com>
Cc: Stephen Tweedie <sct@redhat.com>
Subject: Re: ext3fs 0.0.5d and reiserfs 3.5.2x mutually exclusive
Date: Mon, 8 Jan 2001 16:43:45 +0000	[thread overview]
Message-ID: <20010108164345.A2431@redhat.com> (raw)
In-Reply-To: <20010104135044.A5097@emma1.emma.line.org>
In-Reply-To: <20010104135044.A5097@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Thu, Jan 04, 2001 at 01:50:44PM +0100

Hi,

On Thu, Jan 04, 2001 at 01:50:44PM +0100, Matthias Andree wrote:
> I just tried to patch ext3fs 0.0.5d on top of a 2.2.18 that already had
> reiserfs 3.5.28 and failed, there are overlapping patches in fs/buffer.c
> that I cannot resolve for lack of knowledge how buffer.c and journalling
> are supposed to fit together.
> 
> I reported ext3fs and reiserfs incompatibilities quite some time ago.

I know, and the answer is still the same: removing the extra debugging
stuff and buffer.c code from the ext3 patches is on the todo list but
is much lower priority than finishing off the tuning and user-space
code for ext3-1.0.

--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-08 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 12:50 ext3fs 0.0.5d and reiserfs 3.5.2x mutually exclusive Matthias Andree
2001-01-08 16:43 ` Stephen C. Tweedie [this message]
     [not found] <200101041815.f04IFkn31259@webber.adilger.net>
     [not found] ` <69180000.978632467@tiny>
2001-01-06 11:26   ` Matthias Andree

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=20010108164345.A2431@redhat.com \
    --to=sct@redhat.com \
    --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.