2009/1/21 Andy Levy <andy.levy_at_gmail.com>:
> On Wed, Jan 21, 2009 at 15:12, Propane13 <johnkharvey_at_gmail.com> wrote:
>> Anyway, I was downloading from a remote repository, and found an issue
>> (that I have gotten to the root cause of).
>> Basically, I would download code through a VPN connection and
>> TortoiseSVN. When trying to checkout a label from the server, I would
How does downloading through a VPN work? Are you using file://
protocol to access a drive on a remote computer? That is not a good
way of working and we would seriously recommend setting up a proper
server process. It won't fix the case sensitivity but it will be a lot
safer and hopefully faster too.
> Short version: Subversion is case-sensitive, Windows is not. Every
> other platform Subversion runs on is case-sensitive, Windows is not.
FWIW, I believe OS-X is, like Windows, case-preserving but not
case-sensitive. No help at all, just raising it before anyone else
> It's known, it's well-documented, it's not going to change.
> Subversion will not be changed to become case-insensitive. People
> running repositories which will be shared with Windows users need to
> be sensitive to the case-insensitivity of Windows, and monitor their
> repositories for filename collisions. There's even a hook script
> designed to check for exactly these situations on pre-commit.
What he said. Even if you can use a case-sensitive partition on
Windows, I'm not sure that will help. I'm pretty sure SAMBA mounts
have the same problem.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-21 23:52:25 CET