Greg Stein wrote on Wed, Feb 29, 2012 at 03:50:19 -0500: > On Wed, Feb 29, 2012 at 03:03, Daniel Shahaf <[email protected]> wrote: > > Can someone create a 'svnmucc' component please? > > Added. >
Thanks. > >... > > The test suite relies on it, > > Hmm? When did that happen? I can just as readily claim that reliance > as a bug, than to say we should make it a standard tool. > svnmucc_test.py has been promoted to subversion/tests/cmdline/svnmucc_tests.py and svntest.actions.run_and_verify_svnmucc() has been written. Last week I used one of them in a test (though I may have been able to use plain 'svn' too and a working copy). > > ASF infra now relies on it, > > Not our problem :-) > I thought some people here would find this a good reason -- I'm not sure whether I'm one of them. > > it's about to > > have its own issue tracker component... > > You don't get to claim this one. I made a component, but that has no > bearing on whether it is a first-class tool or not. svnmerge.py has > had a component for ages. > OK. > >... > > I'll get it done. > > Please wait for some consensus before changing the product like that. I thought we had had consensus and were waiting for someone to have the cycles. If I was wrong I apologise. In the meantime I started a branch for this work, and I won't merge it until consensus has been determined. Cheers, Daniel
