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

Re: API review: "repository relative URL" or "relative repository URL"

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Wed, 20 Mar 2013 09:43:13 -0400

On 03/20/2013 08:21 AM, C. Michael Pilato wrote:
> On 03/20/2013 12:23 AM, Branko ─îibej wrote:
>> On 19.03.2013 21:38, Julian Foad wrote:
>>> C. Michael Pilato wrote:
>>>> svn_path.h added two new APIs since 1.7.x, svn_path_is_repos_relative_url()
>>>> and svn_path_resolve_repos_relative_url(). These functions have in common
>>>> this nomenclature of a "repository relative URL". But elsewhere, I see
>>>> references to a "relative repository URL". Do we have a preferred syntax
>>>> for those ^/-prefixed things? The book refers to them only as "relative
>>>> URLs" at this point, but if we decide one way or another I'm happy to
>>>> reinforce our decision in the svnbook text.
>>> I had a hand in their creation, and I call them "repository-relative URLs".
>> I tend to agree with this term, because "relative URL" already has a
>> widely accepted meaning that is noticeably different from our usage.
> Okay, that all works for me. The hyphenated form helps bind the "relative"
> to the "repository" as opposed to the "URL", which is precisely the
> ambiguity I was hoping to clear up.

Related follow-up: should we change the output of 'svn info' so that
instead of:

   Relative URL: ^/trunk/en/README

it prints:

   Repository-Relative URL: ^/trunk/en/README

Or is that just obnoxious?

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2013-03-20 14:43:52 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.