nomadbyte

4 ms·

1. 1.▲
   by nomadbyte 10y ago

   Perhaps another factor for minor popularity of Fossil SCM is a lack of plugins for major IDEs. I don't believe this should be such an obstacle, as most plugins implement only a part of SCM client features, thus asking you to resort to
2. 2.▲
   by nomadbyte 10y ago

   Seems like you were trying to create a centralized server, akin to GitHub or ChiselApp to serve as a main repo and registration site, allowing users to self-register. Fossil as such does not need a central server; each user may just as well
3. 3.▲
   by nomadbyte 10y ago

   IMHO, no need to actually mirror. You may simply keep the same project under both Git and Fossil, just add ".fslckout" and "_FOSSIL_" to your .gitignore. 1) Setup Git repo on GitHub. 2) Clone the Git repo. 3) Create loca
4. 4.▲
   by nomadbyte 10y ago

   Indeed, a Fossil repo is actually a SQLite db, one you may as well open and tinker with (at your own risk :). By the same token, it's just as easy to back these repos up, as much as copying the db-file. Or automatically push to a remot
5. 5.▲
   by nomadbyte 10y ago

   Version control debates, why?? I think everyone agreed that having an SCM on a project is a must. Everyone most likely is using some SCM already, often-times the choice is made by someone else upstairs or in the history. Git, bzr, hg, svn,