[Svnmerge] [PATCH] fix for rev printing bug in svn status

Dustin J. Mitchell dustin at zmanda.com
Tue Jun 19 19:37:34 PDT 2007


I will take a look at the patch when I get a chance, but I have some
initial reactions to your post:

On Tue, Jun 19, 2007 at 04:14:18PM -0600, lsuvkne at onemodel.org wrote:
> Hi. I'm presenting the patch to this list for feedback, before deciding if I 
> should send it on to the subversion dev list.

FYI, the developers there have pretty much ignored my repeated attempts
to submit patches.  They're all working on Subversion 1.5, which has
merge tracking built in, and I think svnmerge.py is not even interesting
enough to read a patch for.

I don't want to foment a rebellion, but is it feasible to propose a
fork?  That is, to move the snvmerge directory out of the svn.tigris.org
and to SourceForge or Google Code or something?

I'd volunteer to manage something like that, if folks are interested.

> There are 3 tests that fail, but they seem to also have been failing in the
> version currently in trunk, and I didn't address them.

I saw the same thing.  There's traffic on this list from a few months
about that, but I don't think the known failures were ever corrected.

Dustin

-- 
        Dustin J. Mitchell
        Storage Software Engineer, Zmanda, Inc.
        http://www.zmanda.com/



More information about the Svnmerge mailing list