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

Re: 1.8 new public API review (mostly) complete.

From: Ben Reser <ben_at_reser.org>
Date: Mon, 1 Apr 2013 10:34:46 -0700

On Mon, Apr 1, 2013 at 9:27 AM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> First we need to clarify what "@a path (a file,)" means. From the discussion below I gather "a file" means an absolute local filesystem path, so let's say so.

Yes absolute OS filesystem path. I prefer saying OS filesystem path
because it may not actually be local if it's some sort of network
mount, so I think local clouds the issue. I'm not sure what we've
been using in our API docs, but if we've been using local that way
then that's fine.

> Erm, not so trivial: svn_path_resolve_repos_relative_url() assumes the "repos-relative URL" is URI-encoded, whereas a relpath is by definition not URI-encoded.

Good point.

> That could work, but it is *much* nicer in my opinion to get rid of the relative-URL option and get rid of the 'repos_root' argument (which was Ben's original suggestion IIUC). It's simple, cheap, and easy.

Yes, that was my original suggestion. I'll go ahead and do that.
Received on 2013-04-01 19:35:25 CEST

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