GitButler Blog

I'm using these options https://blog.gitbutler.com/how-git-core-devs-configure-git and I'm happy with it

I had configured that one ever since reading this very helpful article, which I suspect I discovered through HN a while ago: https://blog.gitbutler.com/how-git-core-devs-configure-git

I've been getting my family members to start vibe coding. In my experience, claude works very well but the biggest issue is actually installing all the necessary tools. So I created a little setup script that MacOS users can use to get up-and-running quickly. It basically sets them up with a development environment similar to the one I use personally. It uses the git settings from https://blog.gitbutler.com/how-git-core-devs-configure-git , helps them set up their username/email, downloads Ghostty, VSCode, fnm and pnpm, etc.

GitButler handles all of this pretty automatically, if you don't want to deal with the Git gymnastics needed here. https://blog.gitbutler.com/stacked-branches-with-gitbutler

GitButler relicensed[1] to FSL, so it's source-available now, open-source after two years. [1]: https://blog.gitbutler.com/gitbutler-is-now-fair-source/

This war was over around about the time I started, but my take on it is that it's all a bit intermixed and Mercurial lost because bitbucket caved and did git hosting [2], but git won beacuse of github and heroku [1][2] [1] https://www.koyeb.com/blog/herokus-free-tier-legacy-the-shoulders-we-s… [2] https://blog.gitbutler.com/why-github-actually-won/

> In Retcon, if a commit move results in a conflict, that doesn't matter; you can keep making changes to your history anyway, and then resolve any remaining conflicts when you're ready. I didn't realize Retcon could do this from the website, nice! I wonder how similar your approach is to [jj's approach to conflicts]; whether you reinvented the same way of modelling conflicts in the repo or use a different one. (See also the link to the technical docs from that page) https://gitbutler.com/ also [borrowed this idea] from jj. [jj's approach to conflicts]: https://martinvonz.github.io/jj/latest/conflicts/ [borrowed this idea]: https://blog.gitbutler.com/fearless-rebasing/ So, there are several tools exploring these ideas, but there are interesting differences in (for example) how close to Git each of these approaches stays.

Microsoft uses git for Windows repository pretty successfully. It started with custom VFS implementation and fork of git but by now everthing is upstreamed and VFS is not used anymore. https://blog.gitbutler.com/git-tips-3-really-large-repositories/

https://blog.gitbutler.com/rss/ most of the time trying the main URL + /rss works also the tag is there <link rel="alternate" type="application/rss+xml" title="GitButler" href="https://blog.gitbutler.com/rss/">

https://blog.gitbutler.com/series-a likely has a large part to play in it. By which I mean, what do we imagine a16z thinks of the [L]GPL? My brief experience in a startup exposed to them is that a16z seems willing to fund "infrastructure" projects more than most, but they did seem to have a ready set of answers on what "open source" means in that context. (If someone can find me an a16z funded team that published copylefted code, I'll take this back.) EDIT: Ok, i'll eat my hat, Gemini found me some counterexamples Element (Matrix): The company behind the decentralized Matrix communication protocol is on a16z's investment list. In late 2023, Element relicensed its core software (including the Synapse server and its clients) to AGPLv3. Uniswap Labs: A massive cornerstone of the a16z Crypto portfolio. They published the Uniswap V2 smart contracts under GPL-3.0 (though they later shifted to a Business Source License for V3 and V4). a16z Themselves: In an ironic twist, a16z's own crypto engineering team maintains a public GitHub repository (a16z/a16z-contracts — a library for Solidity contracts) that is literally licensed under AGPL-3.0.