I'm trying to understand why it would be a good thing to do what fossil
currently does.

When I do "fossil mv x y", it "marks" the files as renamed.  But then I
can easily get in a state where fossil is confused (happened just today
in fact), if I don't copy the "x" to "y".

What is the reason "fossil mv" works this way, and can there at least be
an option to perform a physical file move?  The same question applies to
"fossil rm"
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to