Re: Issue with svn log, maybe more...

On 28 September 2004, barry.kaplan@gmail.com said:
> Thanks that did the trick a there was a ^H in the log.

I stumbled across this about a year-and-a-half ago. Asked on the list
at the time, and I *think* there was some consensus that this is a
cvs2svn bug. (At the very least, it should crash and burn on
encountering control characters in log messages.) Can't remember if a
filed a bug report at the time, but a quick search of the cvs2svn bug
database (err, sorry, "issue tracker" ;-) turns up nothing.

You might want to file a bug report now and save future people the
headache that you and I both suffered. It doesn't take a "pile of Perl
goo" (nice turn of phrase) to put control chars into a CVS/RCS log
message -- clumsy fingers when entering a log message in emacs will do
it too.

I imagine this one will be pretty easy to reproduce and easy to fix (as
long as everyone agrees that "cvs2svn dies horribly on control char in
log message" is the correct behaviour.)

        Greg

-- 
Greg Ward <gward_at_python.net>                         http://www.gerg.ca/
We have always been at war with Oceania.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org