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

Change in handling of paths in commit notifications

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-04-26 19:16:47 CEST

There seems to be a behavior change in trunk with commit notifications
when absolute paths are provide to the command.

It appears the commit code looks at the current directory and the
absolute path being committed and tries to turn that into a relative
path. An initial question here might be why? It does not appear that
other commands do this. Let's hold off on that question for now.
Testing on Windows it appears that even 1.4.3 does this, so it is not
new code with trunk. In fact Windows gives the same results with
1.4.3 and trunk.

Assuming current directory is C:\svn\bin and this command:

svn ci -m "" C:\wc\project\folder\file.ext

You get this output:

Sending wc\project\folder\file.ext
Transmitting file data .

Note that the common part of the current directory and the path is C:\
and it has been removed from the output.

Let's move to OSX and 1.4.3:

Current directory is /usr/local/svn-1.4.3/bin

svn ci -m "" /Users/me/wc/project/folder/file.ext

You get this output:

Sending /Users/me/wc/project/folder/file.ext
Transmitting file data .

But, when the same command is run with 1.5 you get this output:

Sending Users/me/wc/project/folder/file.ext
Transmitting file data .

Note that the leading "/" has been removed similar to the way that C:\
was removed on Windows.

I have already fixed Subclipse to deal with this, but I can imagine it
might be considered a bug. Personally, I would probably prefer to
just consistently get absolute paths passed back to the command when
absolute paths were input to it.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 26 19:16:55 2007

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.