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

Re: JavaSVN (Re: Subversion Branding / "whole product" (Was: Re: SmartSVN - a new Subversion client))

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-26 00:16:39 CET

On Feb 25, 2005, at 4:16 PM, Travis P wrote:
> When the IETF develops protocol standards, if I recall correctly, they
> like two independent and interoperable implementations. It seems to
> me really neat and a contribution to the overall project that JavaSVN
> has been able to provide such an independent and interoperable
> implementation of the client/server protocol.

It's not just about the protocol. If I checkout a working copy using
JavaSVN, can I then use the regular 'svn' C program against that
working copy with no problems? What about the opposite scenario?

If we ever standardize into a spec, there will be much more than just a
protocol to document. (FWIW, though, the protocols *are* documented,
as well as the working copy format. The only documentation of weird
edge-case behaviors seems to exist in the comments in our regression

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 26 00:17:52 2005

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.