On 7/22/2014 10:22, Ron W wrote:
Yes, I know that modern versions of Windows
support symlinks, but I was getting eros from the command so I just did
nested check outs instead.
Native symlinks on Windows are a mess.
First, the mklink command has its options in reverse order as compared
to ln(1). And if your response to that is to shrug it off as just an
unimportant cosmetic choice, observe that the ln(1) option order is the
same as the cp(1) option order, which is the order copied by DOS's copy
command. So yeah, mklink is objectively *backwards*.
The second annoying mklink restriction -- and the one that probably bit
you -- is that you not only have to be in the Administrators group to
run it, you have to do so from an elevated command shell.
If you're using Cygwin on Windows, it's a whole lot easier to just use
its emulated symlink mechanism.
As for the poll, I've never used --nested, but I'm a Fossil newbie, so
let that count for a quarter vote at most.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
