On Tue, May 10, 2011 at 15:28, Bert Huijben <b...@qqmail.nl> wrote: > > >> -----Original Message----- >> From: Greg Stein [mailto:gst...@gmail.com] >> Sent: dinsdag 10 mei 2011 11:18 >> To: dev@subversion.apache.org >> Subject: Re: [PATCH] WC DB verification 1 >> >> >... >> > I would suggest adding a new function for this purpose; and maybe a >> separate >> > program to call it for our beta cycle. >> >> Please... not another program. There was also a recent call for 'svn >> upgrade' to be separate. It really sucks to have an installation smear >> a dozen programs into your system ("which one do I use? for what? hmm. >> for this? ... um..."). We already have a notion of subcommand. That is >> normal, expected, and understood. We can continue to use that without >> fear of user misunderstanding. In fact, it is probably best to tell >> users "just use 'svn'. you don't need anything else". (administrators >> are another thing, but we don't have to complicate their lives, too! >> ... we have too many executables) > > I'm still not sure if this tool should survive outside the subversion > developer world. > > And I didn't hear you suggest that we should include all the > svnraisetreeconflict and entries-dump and like programs in 'svn'. > > I would suggest creating the API inside a library so other tools may use it, > and *for now* enable its use via a separate program. > Or create an option for cleanup command. Something like "svn cleanup --verify"
-- Ivan Zhakov
