From: Tom Vier <tmv@comcast.net>
To: reiserfs-list@namesys.com
Subject: Re: 2.6.4 corruption
Date: Mon, 22 Mar 2004 19:50:40 -0500 [thread overview]
Message-ID: <20040323005040.GB3975@zero> (raw)
In-Reply-To: <405F84C9.6020406@free.fr>
On Tue, Mar 23, 2004 at 01:28:57AM +0100, Vince wrote:
> and it looks like the second patch depends on the first one when wanting
> to modify the same file (therefore a reject with --dry-run)...
d'oh. i should've realized that. everything's fine now.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
prev parent reply other threads:[~2004-03-23 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 0:55 2.6.4 corruption Tom Vier
2004-03-22 1:23 ` Tom Vier
2004-03-22 11:21 ` Dieter Nützel
2004-03-23 0:08 ` Tom Vier
2004-03-23 0:28 ` Vince
2004-03-23 0:50 ` Tom Vier [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=20040323005040.GB3975@zero \
--to=tmv@comcast.net \
--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.