[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Issue 1954

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2006-07-18 17:14:12 CEST

On Tue, 2006-07-18 at 10:44 +0200, Philipp Marek wrote:
> On Sunday 16 July 2006 11:21 Philipp Marek wrote:
> > But the question would remain! It's not possible to allow *every* character
> > in filenames, else eg. the dump format may be damaged (by \n in filenames).
> > Similar a \r may cause problems on win32, and so on ....
> To reiterate: It *is not possible* to allow all characters, so there has to be
> some encoding/decoding.

Encoding and decoding is only one answer; disallowing problematic
characters is another, and I think that option is more palatable to

Retroactively introducing an encoding and decoding mechanism for paths
also creates some versioning issues, particularly with the dump format.
If I have a file named tab\x09name today, that fits in the dump format
just fine, but you'd be changing the meaning of said dumpfile in future
versions of Subversion.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 18 17:15:45 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.