From: "ismail (cartman) donmez" <kde@myrealbox.com>
To: Con Kolivas <kernel@kolivas.org>, gutko@poczta.onet.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: supermount
Date: Thu, 15 May 2003 09:16:47 +0300 [thread overview]
Message-ID: <200305150916.47890.kde@myrealbox.com> (raw)
In-Reply-To: <200305150104.23616.kernel@kolivas.org>
On Wednesday 14 May 2003 18:04, Con Kolivas wrote:
> Watch this space. There's some work happening with 2.4 bug testing with
> some supermount development work and then 2.5 will follow soon enough. The
> current version (call it a fork?) of 1.2.5 has a problem with filesystems
> that can write the same file with different case (eg vfat writing file.c
> and File.c) but can be found at the new sourceforge home:
> http://supermount-ng.sf.net
Thanks for the link . I can test it on 2.5.x .
Regards,
/ismail
--
Brain fried -- Core dumped
next prev parent reply other threads:[~2003-05-15 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 13:40 supermount ismail donmez
2003-05-14 15:04 ` supermount Con Kolivas
2003-05-15 6:16 ` ismail (cartman) donmez [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 21:04 Supermount Lasse Kärkkäinen / Tronic
2005-07-21 21:41 ` Supermount Francois Romieu
2005-07-21 21:50 ` Supermount ioGL64NX
2005-07-22 16:38 ` Supermount Lasse Kärkkäinen / Tronic
2005-07-23 10:47 ` Supermount Oliver Neukum
2005-07-23 17:35 ` Supermount Lasse Kärkkäinen / Tronic
2005-07-24 1:44 ` Supermount Ian Kent
2005-07-24 1:48 ` Supermount Ian Kent
2005-07-24 20:05 ` Supermount zhilla
2003-05-14 13:41 supermount ismail donmez
2003-05-14 13:54 ` supermount Alan Cox
2003-05-13 16:30 supermount Maciej Górnicki
2001-06-25 16:50 supermount Sam Halliday
2001-06-26 0:30 ` supermount Steve Kieu
2001-06-30 5:17 ` supermount John Silva
2001-06-25 16:44 supermount Sam Halliday
2001-07-07 1:43 ` supermount Dj_RzulF
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=200305150916.47890.kde@myrealbox.com \
--to=kde@myrealbox.com \
--cc=gutko@poczta.onet.pl \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/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