On 4/18/15, Steve Stefanovich <s...@stef.rs> wrote: > How about if the fork happens, simply change the tag automatically to > 'fork-trunk' (i.e. prefix the existing repeating tag(s) with 'fork'), or > just tag it as 'fork', on commit? >
When the artifacts that comprise a fork are received, the server has no way of knowing that new artifacts that resolve the fork (either by merging or by moving it onto a branch) will not be received within the next few milliseconds. Hence, what you suggest could result in strange and mysterious changes occurring to the check-in topologies during a push. Very undesirable, I think. -- 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
