Hey guys,

just wanted to say thanks to everyone who works on fossil, it's really a great tool. A minor thing that occured to me today. I was working on a file, then noticed that my repository was in the checkout directory. I wanted to move it so it wouldn't interfere with bash completion anymore. fossil close reported that "there are unsaved changes in the current checkout". I stashed the changes away, then did fossil close again, without any errors this time. After I moved the repo and did fossil open, the stash was empty. This makes sense since the stash is tied to the checkout. Right? It's probbably a rare use case, but maybe fossil close could warn about stashed, uncommitted changes.
By the way:
This is fossil version 1.26 [c9cb6e7293] 2013-06-18 21:09:23 UTC
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to