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

Bug with Special Character in log message

From: <frank.j.gilroy_at_accenture.com>
Date: Tue, 22 Jul 2008 13:29:53 -0500

Hello folks,

 

We're running across an issue when using svn log on one of our
repositories. We regularly execute a command like the following for
reporting purposes:

 

svn log --xml --non-interactive https://our.server.com/svn/TEST/

 

When we run this command it truncates the output at a revision that has
a strange character in the log message. It fails to put the closing
</log> in the XML and spits out the following message:

 

svn: REPORT of '/svn/TEST/!svn/bc/154': 200 OK

 

I noticed that the revprops file for the offending revision contains a
special character and gets recognized as ISO-8859 as opposed to ASCII
like all of the rest of the 7000+ revprops files. I have attached that
revprops file.

 

I'm told that newer versions of subversion don't allow log messages with
bad characters. But I'm wondering if it could be patched to file more
gracefully for existing log messages with bad characters. Our audit
folks don't want us going back and mucking with old log messages.

 

Thanks.

 

 

 

Frank Gilroy

Accenture

(610) 761-8176

AIM: fjgilroy71, YAHOO: fjgilroy

frank.j.gilroy_at_accenture.com <mailto:frank.j.gilroy_at_accenture.com>

 

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org

  • application/octet-stream attachment: 442
Received on 2008-07-23 01:14:20 CEST

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.