2011/9/1 Jacek Cała <jacek.c...@gmail.com> > If fossil can't process the mv+edit combination when diffing neither > it moves files on disk, what is the purpose of mv then? >
That seems like a fair question, but i'm not qualified enough to say anything clever in response :). > > A mv+edit combination could have a non-0/100% diff, i guess. > > IMHO, this is what user (me) would actually expect. > Agreed, but i can't say the current behaviour bugs me at all. When i rename i file i commit it to a clean state then mv+commit it. But that's just a personal workflow preference, and the above behaviour would arguably be more intuitive for most users. It's kinda like the "commit --branch ..." vs "branch new, then commit" question/thread which came up a month or two ago. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
