On 5/5/18, Dingyuan Wang <gumb...@aosc.io> wrote:
>
> The fossil mv command seems can't rename a directory.
I thought somebody had fixed that. But maybe not. What version are you using?
Renaming directories, or even files, is not something that I do very
often, as I find that it disrupts the history of the project, making
it more difficult to answer questions like "why and when was this line
of code inserted?" If the code keeps moving around, it becomes more
difficult to track which file that line of code started in. To
illustrate the infrequency with which I rename files, here is a
complete list of file rename operations that have occurred on the
SQLite project during the 8.7 years that it has been tracked by
Fossil:
https://sqlite.org/src/test-rename-list
That's a short list when you consider that there have been 13616
check-ins in that same time period.
The above sounds like I'm making excuses. I shouldn't be. Fossil
*should* rename the directory for you without giving you any grief.
It should "just work". I'm sorry that didn't. That needs to be
fixed. (You can submit patches if you like :-)) The purpose of my
long reply is to point out that renaming is not a frequently used
feature, and is thus more likely to contain shortcoming and bugs,
which you have apparently now discovered.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
