On 2017-04-10 21:36, Scott Robison wrote:
Next I added a.a explicitly (it warned me and I said okay) and
committed. Then I made a change to a.a and it was identified as a
change for the next commit.
So my best guess at the moment is: During one of your earlier attempts
at adding things, you added a bunch of files and committed them to the
repo. Now that those files are in the repo, fossil will not ignore
them because they are part of the repo. If you were to remove the
files from the work directory so that fossil was no longer tracking
them, commit those changes, then try addremove again, it might work
more to your liking.
At least, that worked for me here with a simple little repo with only
a few files in it.
My version: "This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UTC"
I reckon I owe you a beer! ;-)
I haven't tried it yet because soe of the files I should remove are
quite big. I'll try to move them out of the open path later. I'm sure
Visual Studio is going to rebuild its Intellisense SQLite databases
again but this might take a long time for various projects.
Anyway, your suggestion sounds very reasonable (ok, it doesn't sound
reasonable at all to be honest, but I think that's what happened).
After reading your mail I remembered that all files that have been
ignored all along via ignore-glob or --ignore are files I deleted
manually at one point or another.
The files that always go into the repro I've never touched but I'd added
them to the ignore list later.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
