If I want to see what files might change with an 'update', I supply the '-n' option. E.g. fossil update -n
For files that have a merge conflict, the 'baseline', 'original', and 'merge' files get created on my local file system. All other files that would get updated do not get updated (the expected result with the -n option). I would expect that no changes to my file system would occur when using the '-n' option. If this is not a bug, the documentation for the 'update' command should be changed to reflect the actual behavior. Thanks, Marty Backe _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
