For those that are curious about the motivations and implementation, I recommend Stefan Sperling’s EuroBSDCon 2019 talk [1] and its slides [2]. You will find examples of the workflow at around 12:30 or from slide 23.
In short, it builds on top of the same protocol and format as Git and is thus compatible. But aims to be minimal and primarily serve the mindset and needs of OpenBSD developers. There are however portable releases and as we have seen in the past, OpenBSD software tends to find its way far outside OpenBSD itself: ssh(1), tmux(1), etc.
Git is not insufficient. For various reasons, Git is not a good match for what OpenBSD needs. OpenBSD needs an implementation that uses privsep, pledge, unveil, fits the mindset needed for Theo to accept running it on his own infrastructure, doesn't carry more baggage than necessary, and is a joy and easy to work on for OpenBSD developers independently from third parties. So the options were forking Git or writing something else, and I chose to do the latter.
[1]: https://yewtu.be/watch?v=PRIgeouw7-4
[2]: https://www.openbsd.org/papers/eurobsdcon2019-gameoftrees.pd...
In short, it builds on top of the same protocol and format as Git and is thus compatible. But aims to be minimal and primarily serve the mindset and needs of OpenBSD developers. There are however portable releases and as we have seen in the past, OpenBSD software tends to find its way far outside OpenBSD itself: ssh(1), tmux(1), etc.