Martin Gagnon wrote:
>
> But if I do:
> $ fossil add a_dir_symlink/*
>
> It add the content.
>
> Actually, may be it was intended ?
>
The way it should work (on the branch) is:
1. With allowSymlinks ON, symlinks to both files and
directories are always treated as "normal" content
files. In this case, the --no-dir-symlinks flag
has no effect because they are already disabled.
2. With allowSymlinks OFF and WITHOUT the --no-dir-symlinks
flag, symlinks to files refer to the linked file and
symlinks to directories are traversed into.
3. With allowSymlinks OFF and WITH the --no-dir-symlinks
flag, symlinks to files refer to the linked file and
symlinks to directories are NOT traversed into.
Given the above, my local testing seems to confirm that it
works as intended, including the "add" command.
--
Joe Mistachkin @ https://urn.to/r/mistachkin
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
