From: "Dan Nicholson" <dbn.lists@gmail.com>
To: "Martin Langhoff" <martin.langhoff@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Florian v. Savigny" <lorian@fsavigny.de>,
git@vger.kernel.org
Subject: Re: Can git be tweaked to work cross-platform, on FAT32?
Date: Tue, 19 Dec 2006 15:55:03 -0800 [thread overview]
Message-ID: <91705d080612191555k3dc6a473n4b1e4df2d22880bf@mail.gmail.com> (raw)
In-Reply-To: <46a038f90612170221u4c3b5c2asef378d3d4e159ba7@mail.gmail.com>
On 12/17/06, Martin Langhoff <martin.langhoff@gmail.com> wrote:
>
> Note that under windows you can use ext2 -- haven't used it, and don't
> know how cygwin behaves with it, but it may be *just* what you need to
> avoid case sensitivity problems and have symlink support.
>
> http://sourceforge.net/projects/ext2fsd
>
> http://www.fs-driver.org/
I've used both of these guys, but not the most recent versions. Both
were previously read-only, but now it appears both have write support
from looking at the release notes. Both were a bit heavy handed to get
setup, but a decently computer literate person could probably handle
it. Ext2IFS in particular looks dramatically improved from when I last
used it.
Both worked fine through Cygwin for simple usage. I never did anything
with serious disk usage on either of them, so I can't say how it
stacks up to FAT32 on Linux in terms of really hammering the disk.
A little more reading says ext2ifs can't handle permissions or symbolic links.
http://www.fs-driver.org/faq.html
I don't recall the details of ext2fsd, but I think symbolic links
worked. I'd like to look at this again, but I spend all my time in
Linux at home.
--
next prev parent reply other threads:[~2006-12-19 23:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 15:58 Can git be tweaked to work cross-platform, on FAT32? Florian v. Savigny
2006-12-13 16:39 ` Johannes Schindelin
2006-12-14 5:55 ` Martin Langhoff
2006-12-16 9:51 ` Florian v. Savigny
2006-12-16 11:37 ` Johannes Schindelin
2006-12-17 10:21 ` Martin Langhoff
2006-12-17 14:33 ` Stefano Spinucci
2006-12-17 14:54 ` Johannes Schindelin
2006-12-17 18:16 ` Juergen Ruehle
2006-12-17 19:33 ` Johannes Schindelin
2006-12-18 1:36 ` Stefano Spinucci
2006-12-18 13:38 ` Johannes Schindelin
2006-12-18 14:19 ` Juergen Ruehle
2006-12-19 23:55 ` Dan Nicholson [this message]
2006-12-19 21:57 ` David Lang
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=91705d080612191555k3dc6a473n4b1e4df2d22880bf@mail.gmail.com \
--to=dbn.lists@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=lorian@fsavigny.de \
--cc=martin.langhoff@gmail.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;
as well as URLs for NNTP newsgroup(s).