From: Andrea Arcangeli <andrea@suse.de>
To: J J Sloan <jjs@mirai.cx>
Cc: linux-kernel@vger.kernel.org, linux-lvm@msede.com
Subject: Re: [Fixed] - Repeatable oops mounting snapshots w/ test 10
Date: Wed, 1 Nov 2000 21:34:12 +0100 [thread overview]
Message-ID: <20001101213412.A22947@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.10.10011011214490.12293-100000@mirai.cx>
In-Reply-To: <Pine.LNX.4.10.10011011214490.12293-100000@mirai.cx>; from jjs@mirai.cx on Wed, Nov 01, 2000 at 12:19:31PM -0800
On Wed, Nov 01, 2000 at 12:19:31PM -0800, J J Sloan wrote:
> But why is the "official" release of the lvm utils so buggy?
I guess it was a minor merging typo in the userspace tools and I'm sure Heinz
will solve it shortly now that we're aware of the problem.
Andrea
-
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/
prev parent reply other threads:[~2000-11-01 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 20:19 [Fixed] - Repeatable oops mounting snapshots w/ test 10 J J Sloan
2000-11-01 20:34 ` Andrea Arcangeli [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=20001101213412.A22947@athlon.random \
--to=andrea@suse.de \
--cc=jjs@mirai.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@msede.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox