I've got some work where I've got some files whose names change between commits, but are the same logical entity. For example, if I have a file: libxyz-1.2.txt, which might be a description of libxyz (for version 1.2 in particular), if the name changes to libxyz-1.3.txt for the next commit, what I'll see on [fossil changes] is a missing libxyz-1.2.txt and an extra libxyz-1.3.txt. One simple way to keep all the files tracked is to [fossil rm] the 1.2 file and [fossil add] the 1.3 file, but then the logical continuity of the files is lost. If one does a [fossil mv], the logical continuity is preserved, but I can't think of a nice easy automated way for achieving this for the case of many affected files, or (semi-)complex name transforms.
Are other people affected by this too? Does anybody have any tricks to share? Regards, -bch
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
