On 09/05/07, Julian Kolodko <Julian.Kolodko@silverbrookresearch.com> wrote:
> Thanks for the information on hardlinks under NTFS.
> Unfortunately, as Daniel pointed out, I was using the wrong
> terminology. The links in the original Linux working copy were actually
> symlinks (softlinks) rather than hard links. If they had been hardlinks
> then presumably multiple copies of the same file would have been stored
> in the repository.
> I thought I might be able to sidestep this problem by checking out the
> directory using svn under cygwin. Interestingly SVN under cygwin treats
> symbolic links differently to Tortisesvn. Tortisesvn writes a simple
> text file that gives the location of the target file. When you check
> out using Cygwin/SVN and look at the result under cygwin all the
> symlinks work as you would expect. Under windows explorer the symlinks
> appear as windows links (windows displays a little arrow at the bottom
> left of the icon and the file is a binary file not a simple text file)
> but double clicking on the link doesn't do anything.
Again, this is not specifically TortoiseSVN but the underlying
subversion library. You will get the same with the windows command
> I might try getting access to a Linux system, checkout the directory
> then try moving it to my windows PC using samba. Maybe that will
> replace the symlinks with copies of the target file. If all else fails
> I'll try writing a script to do the job.
A word of warning here. You should not use one working copy with
different OSes, for example if you checkout a WC on a shared drive in
Windows and then access it using the Linux svn client you can run into
trouble. The WC format is not designed to be accessed on multiple
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 9 10:24:29 2007