Re: Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Branko Čibej
On 29.02.2016 20:45, Vincent Lefevre wrote: >>> The problem is that it is too easy to create files with a name using >>> invalid UTF-8 sequences >> File names on disk DO NOT have to be represented in UTF-8. They do have >> to be represented in consistently with the current locale settings. > which

Re: Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Vincent Lefevre
On 2016-02-29 19:57:04 +0100, Branko Čibej wrote: > On 29.02.2016 19:30, Vincent Lefevre wrote: > > On 2016-02-29 17:00:01 +0100, Bert Huijben wrote: > >> The problem is most likely not that they have an invalid utf-8 sequence in > >> their name, but that your settings report that filenames are enc

Re: Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Stefan Sperling
On Mon, Feb 29, 2016 at 07:30:14PM +0100, Vincent Lefevre wrote: > For "svn st", I do not try to access the file. A file with an invalid > name cannot be a versioned file anyway. So, it could also just be > ignored, and outputting a non-fatal warning would be sufficient, IMHO. > Note that even "svn

Re: Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Branko Čibej
On 29.02.2016 19:30, Vincent Lefevre wrote: > On 2016-02-29 17:00:01 +0100, Bert Huijben wrote: >> The problem is most likely not that they have an invalid utf-8 sequence in >> their name, but that your settings report that filenames are encoded in one >> way, while there is a file which name can't

Re: Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Vincent Lefevre
On 2016-02-29 17:00:01 +0100, Bert Huijben wrote: > The problem is most likely not that they have an invalid utf-8 sequence in > their name, but that your settings report that filenames are encoded in one > way, while there is a file which name can't be expressed by that format. > > You get this e

RE: Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Bert Huijben
> -Original Message- > From: Vincent Lefevre [mailto:vincent-...@vinc17.net] > Sent: maandag 29 februari 2016 16:24 > To: dev@subversion.apache.org > Subject: Unversioned files with invalid UTF-8 sequence in name confuse svn > > With: > > svn, version 1.9.3 (r1718519) >compiled Jan

Unversioned files with invalid UTF-8 sequence in name confuse svn

2016-02-29 Thread Vincent Lefevre
With: svn, version 1.9.3 (r1718519) compiled Jan 16 2016, 04:46:46 on x86_64-pc-linux-gnu I have a working copy where "make check" has created files whose name contain invalid UTF-8 sequences. The consequence is that such files confuse svn: $ =svn st svn: E22: Error converting entry in di

RE: Outdated ./subversion/libsvn_ra_serf/README

2016-02-29 Thread Bert Huijben
> -Original Message- > From: Stefan Fuhrmann [mailto:stef...@apache.org] > Sent: zondag 28 februari 2016 19:23 > To: dev > Subject: Outdated ./subversion/libsvn_ra_serf/README > > Hi all, > > The first section of that file looks like a keeper > but most of the status info is horribly o