From: Christoph Hellwig <hch@infradead.org>
To: "Gupta, Deepak (Deepak)" <deepakgupta@lucent.com>
Cc: 'Matthew Wilcox' <matthew@wil.cx>, linux-fsdevel@vger.kernel.org
Subject: Re: Unixware 7.1.1 (vxfs) --> Linux Port
Date: Wed, 22 Sep 2004 15:13:28 +0100 [thread overview]
Message-ID: <20040922151328.A2279@infradead.org> (raw)
In-Reply-To: <4C37CF2D8DF07E4CA6357BAD5EB9A5D7153A8849@oh0012exch004u.cb.lucent.com>; from deepakgupta@lucent.com on Wed, Sep 22, 2004 at 10:03:41AM -0400
On Wed, Sep 22, 2004 at 10:03:41AM -0400, Gupta, Deepak (Deepak) wrote:
>
> I guess I wasn't very clear (my apologies), I meant vxfs read/write support. We have been looking at Freevxfs 0.2 as a possibility and I take it version 0.2 is as good as it gets for now?
Unless you want to pay me (or someone else) to implement additional features
you'll have to use what's there, yes.
next prev parent reply other threads:[~2004-09-22 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 14:03 Unixware 7.1.1 (vxfs) --> Linux Port Gupta, Deepak (Deepak)
2004-09-22 14:13 ` Christoph Hellwig [this message]
2004-09-22 14:24 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-09-22 14:50 Tigran Aivazian
2004-09-22 13:49 Gupta, Deepak (Deepak)
2004-09-22 13:54 ` Matthew Wilcox
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=20040922151328.A2279@infradead.org \
--to=hch@infradead.org \
--cc=deepakgupta@lucent.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
/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;
as well as URLs for NNTP newsgroup(s).