On 25.01.2013 19:39, Simon Large wrote:
> On 25 January 2013 15:57, John Cowan <cowan_at_mercury.ccil.org> wrote:
>> Andy Levy scripsit:
>>> What do you propose be done? Colons are not permitted in file
>>> or directory names on Windows systems. The proper solution is to
>>> disallow creating it in the repository in the first place (and rename
>>> via the repo-browser or URL if you already have it) via a pre-commit
>>> hook script.
>> Alternatively, you can use the Cygwin approach, where the Windows-reserved
>> characters are mapped into U+FF00 through U+FF7F, which are legal but
>> improbable Unicode characters. There is no law that says the names of
>> files in the working copy have to be exactly the same as on the server,
>> just that there be a bidirectional mapping between them.
> You'd have to ask for this on the Subversion users mailing list.
> TortoiseSVN is just a consumer of the subversion working copy APIs.
Won't happen: while U+FF00 through U+FF7F are "improbable characters" as
mentioned, they still can be used. So what happens if there's a file
with those characters in the repository?
Answer: the whole breaks down, the working copy gets corrupted and you
can lose data.
So while the current approach returns an error, the Cygwin approach
doesn't and seems to work better - until you lose data. The SVN way will
never ever lose data.
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 2013-01-25 19:53:38 CET