Re: Problem with version 0.16.1 ?

cmpilato@collab.net writes:

 Andreas Wieweg andreas.wieweg@obbit.se writes:
 
  C:\test:
  svn import file:///c:/repo . -message 'arne'
  svn: Invalid argument
  svn: Safe data:
  Hush
  ... was followed by non-ascii byte 229.
  
  Non-ascii character detected (see above), and unable to convert to UTF-8.
 
 What happens if you do the same thing, but with either -m or --message
 (technically, there is no '-message') ?

Ahh, but what he wrote is equivalent to

svn import -m essage file:///c:/repo . 'arne'

which is a perfectly valid import command :)

It's an interesting mistake to make, perhaps the client should treat a
log message of 'essage' in the same way that it treats a --file log
message that refers to a versioned file, i.e. reject it by default.

As to why Andreas is having a problem, perhaps it simply that the
client is not UTF8 enabled and the current directory contains a file
or sub-directory with a non-ascii name, one starting Hush.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org