I am trying to understand the idea behind FOSSIL_ENABLE_LEGACY_MV_RM.

It has been around for a while, and it is the only compile-time flag that
determines if a setting is hard-coded or if it is obtained from the repository 

It appears that if this is not defined, the "mv" and "rm" commands will
modify the file system under all circumstances.
Given the "--hard" option in these commands anyway, this seems superfluous.
So what is the idea behind the FOSSIL_ENABLE_LEGACY_MV_RM flag?
fossil-users mailing list

Reply via email to