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

Re: [Issue 1118] Changed - Subversion cannot handle paths containing tabs.

From: <cmpilato_at_collab.net>
Date: 2003-01-28 16:35:08 CET

Greg Ward gward@mems-exchange.org writes:

 On 28 January 2003, William Uther said:
  On Tuesday, January 28, 2003, at 06:04 PM, Peter Davis wrote:
  More problems: the escaping functions currently ignores the possibility
  that the input is malformed. It might be some work to make all the
  callers handle the errors, but should:
  * xml_escape return error if the input contains unescapable chars (all
  ASCII control chars)
  This translates to, svn will not be able to handle files with control
  chars in their name, right?
 It also means Subversion cannot handle log messages with control
 characters in them. This came up because one of our CVS log messages
 somehow had a Ctrl-D in it; cvs2svn happily converted this to a
 Subversion log message, but we were unable to use the resulting
 repository because one log message for one file resulted in bogus

Aaaactually, this particular change doesn't mean that Subversion cannot
handle log messages with control characters. The fact that we don't
base64 encode (or otherwise do binary-to-text conversion on) our log
messages is what causes the problem you saw. It's a known issue, and
libsvn_ra_dav is dotted with comments like: /* ### urk. this value
isn't binary-safe... */

 Why yes, I have filed a bug report on this... ;-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:22:06 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.