[Default] On Tue, 11 Apr 2017 21:25:31 +0100, Thomas <tho...@dateiliste.com> wrote:
>On 2017-04-11 21:04, Ross Berteig wrote: >> The fossil addremove command is a convenience command that scans the >> tree, obeying some of the glob settings, and applies fossil add and >> fossil forget command as needed to make the list of files now in the >> repository consistent with the settings and the directory tree in the >> working checkout. > > That's right. This means it defeats the idea of using rm beforehand, as > addremove invokes another add for the very same file later on, adding it > again. That's why this doesn't work. I've tried that too. In your use case, I wouldn't blindly addremove and commit, addremove has a --dry-run option for a reason. Use it, setup the required ignore filters, versioned or not. Then fossil addremove --dry-run until satisfied. After the final fossil addremove, check the "fossil ls" list of managed files; "fossil forget" any files you don't want before finally committing. I would say you were in a hurry and only made a beginners mistake, like we all did, and there is no need to change anything. I admit the insignificance of --ignore and the ignore-glob setting on managed files could be stressed a bit more in the docs. -- Kind Regards, Kees Nuyt _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
