[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tree conflicts raised by third-party software

From: Mark Phippard <mphippard_at_collab.net>
Date: Fri, 9 Jan 2009 10:08:26 -0500

On Fri, Jan 9, 2009 at 10:01 AM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> David Glasser wrote:
>> Wait, we're documenting svn_wc__something as something third-party
>> developers should use and rely on???
> Negative. We're documenting it as something only to be used
> intra-library within core Subversion.
> Let me try to explain what we are trying to do.
> We are helping third-party developers to experiment with some non-public
> guts of Subversion 1.6. The example code which is called "svnraisetc"
> effectively shows how to build a modified Subversion that exposes a
> public interface to this API. The example tool is not for end users, and
> it is tied to one particular source code release and not subject to our
> forward compatibility guarantees.
> This is like one developer helping another: "Here, if you want to
> experiment with using Subversion's guts, try this... And if you like it,
> you could help us to stabilize it and make it public."
> Is there a part of that scenario that is wrong for the project, or are
> we just using the wrong labels or something?

I suppose worst case if people object we coud just keep the source for
svnraisetc out of our tree. I do not see why we should have to do
that though.

Mark Phippard
Received on 2009-01-09 16:08:48 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.