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

Re: Correction -> Malformed XML output from svn status command

From: Joakim Birgerson <joakim_at_birgerson.com>
Date: Wed, 28 May 2008 09:29:34 +0200

Hi again,

your support is greatly appreciated! When I discovered the mentioned bug I
was definitely in a "Priority P2" state, so high impact in my case :-(
Current state is that I've coded around the problem. I don't have the
statistics to determine the probability for other to encounter the same
thing, but I think 'xml' often is perceived as the "safe and stable"
approach and creates more bad will when failing. For this reason I suggest a
back port.

I've looked at the enhanced issue list on your site and it looks good! Also
tried the search function at
http://subversion.tigris.org/project_issues.html (summary search) and it
works as well (not least important when the issue list grows).


2008/5/27 Karl Fogel <kfogel_at_red-bean.com>:

> Stefan Sperling <stsp_at_elego.de> writes:
> >> However, the results page seems perfectly functional, and I counted that
> >> all 2850 issues were there.
> >
> > Heh. I hope you didn't have to count by hand? :)
> Of course not. I asked Emacs to count for me :-).
Received on 2008-05-28 18:16:16 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.