On Fri, Sep 24, 2010 at 9:26 AM, David Huang <k...@azeotrope.org> wrote: > > On Sep 24, 2010, at 12:17 AM, Nico Kadel-Garcia wrote: > >> On Thu, Sep 23, 2010 at 11:18 PM, Daniel Shahaf <d...@daniel.shahaf.name> >> wrote: >>> Les Mikesell wrote on Thu, Sep 23, 2010 at 12:27:40 -0500: >>>> Am I wrong in thinking that similar accidents happen to everyone >>>> eventually and that a feature to fix them would be desirable? >>> >>> Yes, the feature has its use case. And if you'd like to see it >>> implemented yesterday, that's cool. Just don't assume that everyone >>> thinks the same way please. >> >> Can you actually name anyone who thinks it's not a useful, or >> potentially useful feature? Anyone? > > I suspect what was meant is that not everyone thinks obliterate needs to be > "implemented yesterday" or that it's the "#1 request". I do think obliterate > would be useful, but I personally have not ever needed it in my 2 or 3 years > of administering an SVN repo, and don't forsee needing it in the future.
Indeed. Of course it's (very) useful. But there are other features/improvements/... that are also useful (improved merge-tracking/merging, tree-conflict resolution, repository-dictated auto-props, general performance, working copy robustness, ... to name a few), and depending on your situation you may find some of them more useful/urgent than others. And as always in software development: you can't do everything at once, you have to pick priorities and focus on them. If you try to fix all problems for all people at once, you'll never get anywhere. Right now (for 1.7) the focus is on a better working copy system, which is badly needed for robustness, speed, ... and for all future enhancements that involve the client side. There has been some work on obliterate, but it had to be deferred because more resources were needed to finish the working-copy rewrite for 1.7. I'm sure it will be implemented someday, but it might take some more time ... Like Daivd said, it's still on the roadmap (http://subversion.apache.org/roadmap.html). Also keep in mind that this is an open-source product. Patches and contributions of any kind are always welcome (there are lots of ways to contribute, not only by writing code, see http://subversion.apache.org/contributing.html). The developer community is really friendly, so if you're interested in getting involved (or helping them help you), please do :-). Cheers, -- Johan
