> > I thought forks were blocked by the push in git. What scenario can lead to > dual heads in git? >
By default non-fast-forward pushes (fork in Fossil terms) are blocked. If you have permission to force a non-fast-forward push then you can replace/overwrite the current branch "tip/HEAD" pointer. This most likely means the previous branch "tip/HEAD" pointer is de-referenced (i.e. no longer accessible through a named branch or tag). These original tip/HEAD commits are still in the repository but eventually they will be garbage-collected. There is no *direct* analog of the Fossil fork feature, although you could crudely simulate one, I suppose, with server-side refs. -J
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
