On Fri, Nov 4, 2011 at 5:43 PM, Nolan Darilek <no...@thewordnerd.info>wrote:
> some pushback from Git users. Is it possible to use Fossil in a workflow > with people who would rather use Git/Github? Richard wrote a nice summary of that on Oct 16th which i'll paste in here: --------------- Fossil does not currently support a hierarchical development model very well. It wants everybody to be a peer. It wants all developers to see everything all the time. Fossil strives to avoid a "peeking order" in which some developers are hidden from view behind "lieutenants". This is a more egalitarian model, but also one that does not scale as well. To better support a hierarchy, Fossil would need the ability to sync individual branches in addition to its current behavior of always syncing everything on every sync request. (Recall that I asked for volunteers to implement such a thing a while back.) But adding that feature quickly gets complicated when you then try to figure out how to deal with auto-sync. You could, I suppose, put your local Fossil into a mode where it only syncs the branch you are currently working on or switching to. But what about Wiki and Tickets and Events? Do they get synced or not? Once you leave the comfort of Fossils original model of "everybody sees all the code all the time" then various operational questions of this kind start to come up. --------------- -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
