On Tue, Jul 19, 2011 at 12:18 AM, Jeremy Anderson <[email protected]> wrote:
> Out of curiosity, why are you converting from mercurial? > > I ask because my friends and I adopted fossil and other friends of ours are > asking us why we didn't go with mercurial instead. I didn't really have a > good answer, apart from "fossil seemed smaller (footprint, use-complexity) > and cooler" =) > Some other possible reasons to prefer Fossil over Mercurial: (1) Fossil supports integrated and distributed trouble-tickets, wiki, embedded documentation, and blog entries in addition to versioning your files. Mercurial is a file-versioning system only. (2) The "fossil ui" and "fossil serve" commands are easier to use and provide much more information than the "hg serve" command. (3) Fossil gives you a "timeline" to help track your project. If Mercurial does this, I've never seen it. (4) Fossil is stand-alone; it does not require python to be installed. Fossil can be run from within a very restrictive chroot jail (which is a nice security feature on servers.) (5) A Fossil repository is a single disk file, not a ".hg" directory containing multiple files. (6) A single fossil repository can host multiple checkouts at the same time. (7) Fossil allows you to amend check-ins with revised timestamps, check-in comments, and/or committers. The original content is preserved and displayed on detailed views, but the revised content is shown on primary displays. (8) Fossil allows check-ins to be moved into new branches after they are committed. (9) Fossil versions branch names so that all contributors have a consistent view of the project. (Git does not do this. I'm not sure how Hg works in this regard - perhap a reader can brief me.) (10) The "fossil all sync" command. (11) Cloning the self-hosting Fossil repo gets you the entire Fossil website, not just the Fossil source code. (One could argue that this is a restatement of point #1.) (12) Fossil has auto-sync mode, which helps to keep all collaborators working on the same code rather than diverging off into their on forks. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
