On 26. 5. 25 15:32, Dr. Thomas Orgis wrote:
Am Fri, 23 May 2025 14:02:46 +0200
schrieb Branko Čibej<br...@apache.org>:
And of course, if we support "^.", we obviously have to support
"^./any/relative/wc/path" in the same way.
Not sure what you mean. ^/ is the repo root. ^./ is the repo path of
the current working directory. Naturally, ^./some/path would be
some/path below the repo location of the current working directory.
Naturally? What if ^./foo/bar is the repos URL of the path foo/bar below
the current directory in the working copy? There are two, equally valid
interpretations, and I sure can't see offhand which one is better.
I don't follow. I guess I need an example. I read this paragraph and
think that you're repeating my interpretation again. Clearly I am
missing the meaning. Given a repository at
svn://some.server/repo
and a working copy checkout of
svn://some.server/repo/sub
in /work/sub, being inside that working copy, makes ^./foo/bar resolve
to
svn://some.server/repo/sub/foo/bar
while ^/foo/bar would resolve to
svn://some.server/repo/foo/bar
What does
^./foo/bar is the repos URL of the path foo/bar below the
current directory in the working copy
mean otherwise?
Consider: if your working copy looks like this:
work
sub
foo
bar
bar
and work/sub/foo/bar is switched (either by 'svn switch' or 'svn
checkout', or is an actual symlink) to work/bar.
If you're current directory is sub, then by your interpretation
^./foo/bar translates to
svn://some.server/repo/sub/foo/bar
But by my interpretation it translates to
svn://some.server/repo/bar
That's a significant difference.
-- Brane
