Re: Tree conflicts raised by third-party software

Hi Tree-conflicts folks,

are we fine with making svn_wc__add_tree_conflict() public for the sake of
the svnraisetreeconflict commandline tool?

Answering `yes' here suggests that ...__remove_tree_conflict() and such
should also go public.

It seems sensible to me to have this public. After all, here we are, wanting
an external tool to manage tree-conflicts in a working copy.

So far we're actually wanting to call this from an external tool, but to
allow so temporarily, until we can handle the situation in question from
within the svn client itself.

Having this public opens doors for nifty tools to-come. Will there be any
beyond svnraisetreeconflict?

Having this public also means having to support it at least until 2.0.
Shouldn't be too hard.

The whole point to this is entirely idealistic. The current state works in
practice, but breaks conventions. I was hoping that it doesn't really weigh
so heavy for contrib stuff...

Opinions?

~Neels

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1012509