Ludovic Brenta wrote:
So Monotone is expecting me to figure out which files it is not
tracking and remove those files before it'll update the working
directory?
Yes, when the update is trying to remove a directory containing such
files.
This is easy to do in a workspace: rm -f $(mtn ls unknown)
I wish I had known that command about 10 minutes ago :-)
Thanks, good to know for the future.
It would be even better if I didn't have to delete these files. Just
because Monotone is not tracking them doesn't mean that they are not
useful. My TODO list, a library, a quick test file, etc. Those are all
legitimate reasons to have files that are not tracked.
Over-all I am concerned about the process of un-doing a commit. What I
want is a functional equivalent of Monotone acting as if I had not done
the commit yet. I don't want it to nuke my files or revert my changes.
Cheers,
Daniel.
_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
