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

RE: Assertion error

From: Simon Heffer <Simon.Heffer_at_microfocus.com>
Date: Tue, 10 Nov 2020 08:52:30 +0000

Looks like my subversion config file is as delivered i.e. all comments. I probably forgot to update it when I got a new machine.
So I guess that means the setting is at the default.
I've also got that thing where on UNIX you get those extra ^M in the file which I guess is all related.
We have a standard file of settings which I will apply now.

Thanks for all your replies btw.


-----Original Message-----
From: Nathan Hartman <hartman.nathan_at_gmail.com>
Sent: 09 November 2020 23:39
To: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Cc: Simon Heffer <Simon.Heffer_at_microfocus.com>; dev_at_subversion.apache.org
Subject: Re: Assertion error

On Mon, Nov 9, 2020 at 4:47 PM Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Nathan Hartman wrote on Mon, 09 Nov 2020 15:49 -0500:
> > On Mon, Nov 9, 2020 at 1:55 PM Simon Heffer <Simon.Heffer_at_microfocus.com> wrote:
> > >
> > > HI Nathan,
> > >
> > > In my content. Not sure why J
> >
> > That could happen when users from multiple OSes interact with the
> > same files. Also, it could happen if you copy-and-paste text from a
> > file with a different EOL style, if your editor does not
> > automatically convert EOLs upon pasting.
> To be clear, it's an assertion error, so it shouldn't happen, period,
> even in the cases mentioned, and the fact that it does happen
> constitutes a bug.

Agreed. I'm trying to narrow down the search for it, e.g., is it in eol-style processing, etc.

Received on 2020-11-10 11:01:09 CET

This is an archived mail posted to the Subversion Dev mailing list.