monotone - Bugs: bug #8923, All uppercase filenames (i.e. MT)...
You are not allowed to post comments on this tracker with your current authentication level.
bug #8923: All uppercase filenames (i.e. MT) upsets vfat (fat32) in Linux
Submitter: | None | ||
Submitted: | Wed 12 May 2004 11:59:17 PM UTC | ||
Category: | working copy | Severity: | 3 - Normal |
Item Group: | incorrect behavior | Status: | Works for me |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | ||
mtn version --full: |
|
Thu 13 May 2010 12:13:48 AM UTC, comment #2: |
Timothy Brownawell <tbrownaw> |
Fri 25 Nov 2005 08:43:10 PM UTC, comment #1: The same or similar issue perhaps seems to bite me using NetBSD's smbfs to manipulate a working dir shared from an NT4 machine (and perhaps other NAS-type fileservers).
|
Daniel Carosone <uep> |
Wed 12 May 2004 11:59:17 PM UTC, original submission:
Ever since I found out about this issue, Ive been alergic to all uppercase filenames. Of course this affects directories too. It apparently is so that all uppercase files written to a fat32 filesystem via Linux (its vfat driver) is changed into lowercase. All lowercase is not touched, as well as all mixed-case filenames is preserved. So Makefile and README.txt is fine, but README and MT would be changed into readme and mt. This will confuse Monotone when it tries to find MT, since this is where it expects to find the control files. I propose to rename MT into either mt, ".mt", Mt or something similar.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-05-13 | tbrownaw | Status | None | Works for me | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
vfat now seems to preserve case with no mount options (possibly related to whatever was done about Microsoft's patents?), and when mounted automatically or through pmount I get the 'shortname=mixed' option which makes it case insensitive (but still case-preserving). So this appears to no longer be an issue. Also, these days NTFS works as a shared filesystem for dualboot.