On Fri, Oct 17, 2014 at 6:30 PM, Ron W <ronw.m...@gmail.com> wrote: > > The main information the "post commit hook" method risks loosing is the > relationship between a copied file and its copy, but Fossil doesn't have a > copy command, so doesn't keep this, though I'm pretty sure it could. >
Err, was too focused on the copied-copy issue. Renaming or moving a file will loose the relationship between the previous and new. This is more common than adding a new source file by copying it. However, despite what the semantics of the dump file make possible, I'm not sure that SVN actually correctly implements rename/move, so this might not be a real issue. I recall this being in the SVN bug list back when I was using SVN.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
