Game of Trees (Got) is a version control system which prioritizes ease of use and simplicity over flexibility.
Got is still under development; it is being developed on OpenBSD and its main target audience are OpenBSD developers.
Got uses Git repositories to store versioned data. Git can be used for any functionality which has not yet been implemented in Got. It will always remain possible to work with both Got and Git on the same repository.
Game of Trees website
OpenBSD is developing Game of Trees because they want a version control system that adheres to OpenBSD coding conventions, implements various OpenBSD security practices, and uses nothing but BSD-licensed code. It’s important to note, as its developers make very clear, that GoT is not in any way intended as a replacement for git.
Dude, Mercurial was RIGHT FRIGGING THERE!
Another “not invented here” syndrome, its really sad!
I loved mercurial very much over GIT, but since everything is GIT those days I eventually flipped too. One has to chose his battles wisely.
Still a perfect example, when the better product lost
Andreas Reichel,
I was a mercurial user too, but it lost the popularity contest and I too gave up on it. Popularity results in a positive feedback loop that concentrates everyone around the very top as unpopular solutions loose users & resources,
When I switched in ~2013, GIt’s branching and tagging model was nicer then Hg’s mechanisms at the time. There was something I looked up, and the instructions were “create a second copy of the repo, then merge changes back into the original repo when done.”
Hg could make a comeback. Finish migrating the codebase to Rust, add better large file support, add support for diffing binary files, better hooks (pre-commit, post-commit), and add the other features Fossil has (integrated wiki, issues, merge requests, etc.) so it doesn’t rely on a code forge for features.
Flatland_Spider,
Well, but even if we grant this is all possible, I don’t see myself going back. Not because I don’t like mercurial personally, but because I don’t live on an island. Whether I like it or not, I live in a git world and now I’m pretty much required to support it. Sadly this makes me part of the network effect keeping alternatives down
@alfman
I don’t see git going away, and it works well when dealing with text files. However, content creation is a niche hg could go after.
Binary heavy projects is not something git is good at. LFS needing a webserver to work is annoying, and I’m not aware of a FOSS DVCS solution for photos, movies, word procesor docs, presentations, etc.
I might go back for my personal stuff. Not relying on a code forge for tickets and things would be really nice. Git will probably get there, as a unified solutions seems to be something people want, but it will take a while.
As for git hooks… One giant shell script is not a particularly elegant solution, or one which easily allows sharing of hooks. Having to manually cultivate a garden of scripts is one of the reasons SysVinit got replaced, so systemd needs to be added to git.
Funnily enough, GoT has a gotd which could be used a prototype for a gitd. Gitd could be started by userspace systemd, and it could handle all of the git operations that code forges are used for, like hooks, notifications, etc.
Flatland_Spider,
Maybe you got this backwards? Git needs to be added to systemd
That wasn’t the point.