On 2016-03-01 17:12:05 +0100, Branko Čibej wrote:
> On 01.03.2016 16:58, Markus Schaber wrote:
> > Hi, Bert,
> >
> > From: Bert Huijben [mailto:b...@qqmail.nl]
> >> From: Markus Schaber [mailto:m.scha...@codesys.com]
> >>> Hi, Brane and Vincent,
> >>>
> >>> From: Branko Čibej [mailto:br...@apache.o
On 01.03.2016 16:58, Markus Schaber wrote:
> Hi, Bert,
>
> From: Bert Huijben [mailto:b...@qqmail.nl]
>> From: Markus Schaber [mailto:m.scha...@codesys.com]
>>> Hi, Brane and Vincent,
>>>
>>> From: Branko Čibej [mailto:br...@apache.org]
> However Subversion doesn't handle that (BTW it would be
Hi, Bert,
From: Bert Huijben [mailto:b...@qqmail.nl]
> From: Markus Schaber [mailto:m.scha...@codesys.com]
> > Hi, Brane and Vincent,
> >
> > From: Branko Čibej [mailto:br...@apache.org]
> > > > However Subversion doesn't handle that (BTW it would be much
> > > > better to
> > > > remember the e
> -Original Message-
> From: Markus Schaber [mailto:m.scha...@codesys.com]
> Sent: dinsdag 1 maart 2016 15:07
> To: dev@subversion.apache.org
> Cc: Vincent Lefevre
> Subject: RE: Unversioned files with invalid UTF-8 sequence in name confuse
> svn
>
> Hi, B
Hi, Brane and Vincent,
From: Branko Čibej [mailto:br...@apache.org]
> >> A fairly plausible cause for getting the wrong representation is
> >> changing the locale for the duration of a script invocation. Another
> >> plausible way is to create files based on the contents of some
> >> script, which
Stefan Sperling writes:
> I agree this is a problem. 'svn cleanup --remove-unversioned' should
> remove such files, but it won't in the current implementation.
Subversion works in non-UTF8 locales. If one normally uses Subversion
in a non-UTF8 locale then non-UTF8 paths on disk can represent ve
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
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
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
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
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
> -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 (
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
13 matches
Mail list logo
