[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: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 27 May 2008 12:09:46 +0200

On Tue, May 27, 2008 at 09:53:04AM +0200, Joakim Birgerson wrote:
> Hi again,
>
> thanks for your reply! Yes, the bug I describe is exactly issue 2887. I
> will try a later version as you suggest.

I think the fix is only in trunk. If you think it would be worth
having in 1.5.1, I can propose it for backport.

To get our current trunk, run:

        svn co https://svn.collab.net/repos/svn/trunk svn-trunk

Then read svn-trunk/INSTALL for information on how to proceed.
Compiling Subversion yourself may take you some time if you've
never done it before -- if you run into any issues, feel free
to mail me privately. Oh, unless you are building on Windows!
Because I haven't got a clue about that :-/

> FYI - I did search the issue list without finding it. It seems you remove
> 'FIXED' issues, but at the same time you have a 'Resolution' column that's
> all empty. As a suggestion, why not keep all issues in the list and add
> the Resolution state in the already existing column? At least in this case
> it would have saved you from my duplicate :-)

You can explcitily select the 'FIXED' issues in the issue tracker
query form. By default, it won't show issues marked fixed (I am
not responsible for this and I could do more about it than
writing mail to tigris.org admins, and then pray).

Thank you,
Stefan

  • application/pgp-signature attachment: stored
Received on 2008-05-27 12:07:25 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.