From: Alan Cox <alan@redhat.com>
To: szepe@pinerecords.com (Tomas Szepe)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre8-ac2
Date: Sun, 12 May 2002 09:19:48 -0400 (EDT) [thread overview]
Message-ID: <200205121319.g4CDJm403128@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020512125151.GD3749@louise.pinerecords.com> from "Tomas Szepe" at May 12, 2002 02:51:51 PM
> Alan, do you suppose you could integrate the new backported NTFS code in
> -ac at some not-so-distant point in time? I reckon that would be a generally
> appreciated decision, as demand of decent NTFS access has existed for
> quite a bit of time already and 2.6 will yet take a while to land.
I'd rather see it stabilize in 2.5 first
next prev parent reply other threads:[~2002-05-12 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 23:47 Linux 2.4.19pre8-ac2 Alan Cox
2002-05-11 23:49 ` Andre Hedrick
2002-05-12 6:40 ` Adrian Bunk
2002-05-12 12:51 ` Tomas Szepe
2002-05-12 13:04 ` Pawel Kot
2002-05-12 13:07 ` Tomas Szepe
2002-05-12 13:14 ` Pawel Kot
2002-05-12 13:19 ` Alan Cox [this message]
2002-05-12 13:22 ` Tomas Szepe
-- strict thread matches above, loose matches on Subject: below --
2002-05-12 10:50 rwhron
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=200205121319.g4CDJm403128@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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