From: Chris Mason <mason@suse.com>
To: Jens Benecke <jens-usenet@spamfreemail.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Chris: mason/patches/data-logging/experimental/2.6.1 upside down?
Date: Tue, 13 Jan 2004 16:56:25 -0500 [thread overview]
Message-ID: <1074030984.32707.989.camel@tiny.suse.com> (raw)
In-Reply-To: <3171912.lEEDWjxvxS@spamfreemail.de>
On Tue, 2004-01-13 at 16:32, Jens Benecke wrote:
> Hi,
>
> the "journal-writer.gz" in the above dir starts with
>
> diff -Nur --exclude=RCS --exclude=CVS --exclude=SCCS --exclude=BitKeeper
> --exclude=ChangeSet linux.dammit/fs/reiserfs/do_balan.c linux.25.1/fs
> reiserfs/do_balan.c
> --- linux.dammit/fs/reiserfs/do_balan.c Fri Jan 9 15:18:17 2004
> +++ linux.25.1/fs/reiserfs/do_balan.c Thu Dec 4 14:20:19 2003
>
> and only REMOVES code, doesn't add anything.
>
> Any chance you patched the wrong way round? ;-)
No, it's supposed to remove code ;-) It's getting rid of some old
debugging cruft that should have been shot long ago.
> oh yes... and is the "data-logging.gz" on the state of the 2.4.23 patches
> that are also in your directory (ie. can I mount with journal=ordered etc)?
Full data=ordered/logging patches are still only in use privately, where
they happily hose filesystems. I'm getting there ;-)
-chris
prev parent reply other threads:[~2004-01-13 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3171912.lEEDWjxvxS@spamfreemail.de>
2004-01-13 21:47 ` Chris: mason/patches/data-logging/experimental/2.6.1 upside down? Dieter Nützel
[not found] ` <31592854.1BIkuMAj52@spamfreemail.de>
2004-01-14 4:11 ` Chris Mason
2004-01-13 21:56 ` Chris Mason [this message]
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=1074030984.32707.989.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=jens-usenet@spamfreemail.de \
--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.