On Mon, Apr 6, 2015 at 12:27 PM, Matt Welland <mattrwell...@gmail.com> wrote:
> Fossil "pretending" to be centralized is a fantastic feature. For me at > least this *is* about factors that make Fossil simple to learn and use. > Autosync is a plus. Forks are a minus. > Fossil doesn't pretend to be centralized, unless you consider multiple checkouts from a single repo to be "pretending to be centralized." Auto-sync is handy. At least when there isn't a lot to pull. Auto-sync helps to avoid forks. But the best way to avoid forks is good communication between contributors. Still, I would like to see the ability to generate a warning when a Fossil server receives a commit against a parent that already has a child on the same branch as the just received commit. I realize this would require a table to maintain "parent to child" relations, but Richard (in a thread about Git) asked about being able to browse the Git timeline in both directions. This suggests that a "parent to child" already exists in Fossil. As for how to propagate fork warnings, I suggest that a special tag be auto-added to the commit (via the existing mechanism for adding tags to commits). Then when a Fossil server receives any such tags, it prints a warning, much like it prints information and error messages during a push/pull/sync operation. Also, the timeline page could distinctly highlight commits with that special tag.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
