As I understand it, fossil currently deletes one file from disk when doing and update if this file has been removed by another user.
For me, it is incoherent that fossil does not do the same on commit. Of course, only for the case that there is a copy of the file in the previous version and that there are no changes in it. In the latter case, no information can be lost, and the file is already contained in the previous version and can be checkout from there if necessary. RR 2012/12/12 Baruch Burstein <bmburst...@gmail.com> > While the numbers may be in favor of the "-s" or whatever option, I doubt > the other behavior would be used zero times. It happens occasionally that I > want to remove a file from version control, but not the actual file
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
