Comment 9 for bug 135234

I have the use case when absolute path for light checkout master branch prevents me to work with the light checkout at all.

I have 2 windows machines in the LAN. The disk of one machine mapped to another one as Z: drive. SO I can work with the remote machine as with local disk.

I have colo workspace with light checkout on remote machine. Of course it uses absolute path and this path points to C:\some\path.

If I try to work with this colo workspace as with object resides on Z: I can't do anything, because light checkout has recorded master branch as the one on disk C:, not Z:. I can't do anything there, at all.