Hi there. I did a blog entry on Fossil, and how it is able to handle a cherry-pick merge scenario that breaks subversion: http://paulhammant.com/2016/06/18/subversion-merge-limitations-not-in-fossil/
Learning curve for Fossil - about an hour. Curiosities: - Having a database name rather than just a .git or .svn folder convention - The 'open' step. Pleasant surprises: - when making a branch, having a 'where from' basis (which I hope is retained) Questions: 1. How do I choose a non 'trunk' name for the initial branch? My test needed a branch called 'one' and another 'two'. 2. Is it possible to do the --record-only merge thing subversion does (Git calls it ‘strategy-ours’, and in Perforce it is ‘accept yours’) ? 3. Where does Fossil top out? Nvidia, Pixar and Google pushed Perforce to multi-terrabytes of HEAD revision, metadate and history. With submodules, git doesn't like to be able 1GB (size of clone), though some field reports suggest 7GB works too. - Paul
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
