Richard Hipp criticizes Git's workflow and design, presenting Fossil SCM as an alternative that preserves complete development history.
The uploader added no description.
Why it's here
3 people recommend this
What people say. Recommended as a thought-provoking critique of Git and an introduction to the Fossil version control system.
a
asix66on Hacker News • Recommends
On “The History of Git”
This reminds be of a talk I watched by Richard Hipp, "Git: Just Say No" 0 where he discusses a "top 10 git enhancements" list, as of the time (4 years ago.) It's a good talk, and caused me to discover Fossil SCM. Sadly I've yet to try/use Fossil, and my teams still use git. 0link to this video
…y, no need for rebasing (at least as a workflow). It sounded nice - refreshing, even. I'm going to start using it for some projects and see how I get on, because frankly, I'm tired of Git and this need to strategise saving copies of my work , because that's basically what it does. Sometimes I even pine for the days I used to version zip files… 1link to this video…
On “Git vs. Fossil: what you should have done vs. what you did”
Here is a (somewhat old) talk by Richard Hipp, the author of SQLite about Git: "Richard Hipp - Git: Just Say No" link to this video I use Git every day, but I am curious about Fossil and have been researching it for a while. I am not planning on changing, as I need to get to the bottom of some data corruption events I have seen in their forums. Not saying it was the fault of Fossil, just that it requires more research on my side. We should not forget Version Management did not start with Git but has a vibrant history that began with SCCS, RCS, CVS, ClearCase, Perforce, SVN, etc... As I used all the systems above except for SCCS and RCS I would advise for some caution here on thinking Git core flows are…