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

Re: svn client api comments

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-03-14 20:54:17 CET

Barry Scott <barry@barrys-emacs.org> writes:

> > These are all problems that one or more of Subversion full committers
> > have been annoyed by -- you aren't alone.
> Is there a design for the API with a depth param, or do you want
> proposals?

I actually started coding this one, but backed out for lack of time.
I think the idea is pretty straightforward -- add a new typedef'd enum
svn_depth_t with values svn_depth_zero, svn_depth_one, and
svn_depth_infinity. Rev all public APIs that currently take
recursive/non-recursive type boolean fields, and make their previous
incarnations pass svn_depth_one or svn_depth_infinity instead (except
in the 'svn commit' case, where non-recursive means svn_depth_one).

> Why is cat so hard to fix? How come diff can do a cat of BASE and a
> cat of WORKING without contacting the repos? Why don't they share
> code?

Never assume that something doesn't work the way you want because it
was too hard. 'svn cat' doesn't work on working copy paths because
there exists for all platforms of interest workarounds:

   $ cat path/to/file
   $ cat path/to/.svn/text-base/file.svn-base
   C:> type path\to\file
   C:> type path\to\file\.svn\text-base\file.svn-base

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 14 20:58:26 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.