You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a rather weird setup in that our loadsets are case-insensitive, yet they're stored on case-sensitive filesystems on the servers. Every now and then, we'll run into the case where Apple or another vendor will change the case of a directory, which means that we wind up with transcripts like this:
d ./foo/Bar
f ./foo/bar/baz
On lapply, clients can't access ./foo/bar/baz because on the case-sensitive server, it's ./foo/Bar/baz. Obviously we can (and do) script around this so that our transcripts match the filesystem, but it would be nice if fsdiff had an option to preserve the case in these situations.
Original comment by: slaunchaman
The text was updated successfully, but these errors were encountered:
We have a rather weird setup in that our loadsets are case-insensitive, yet they're stored on case-sensitive filesystems on the servers. Every now and then, we'll run into the case where Apple or another vendor will change the case of a directory, which means that we wind up with transcripts like this:
d ./foo/Bar
f ./foo/bar/baz
On lapply, clients can't access ./foo/bar/baz because on the case-sensitive server, it's ./foo/Bar/baz. Obviously we can (and do) script around this so that our transcripts match the filesystem, but it would be nice if fsdiff had an option to preserve the case in these situations.
Original comment by: slaunchaman
The text was updated successfully, but these errors were encountered: