Patchwork might be something to keep in mind as an opportunity to install later on if I get overwhelmed by patches. Right now it’d be a complete YAGNI. Also it’s Django.

I like the idea: it doesn’t intrude with the mailing list workflow at all, it’s just an extra “view” of the patches.

In love with the git send-email workflow but just wish those primitive screwheads could stop sending you PRs? Well, wish no more since there is maildir-import-patch and notmuch-import-patch to sort things out for you 💁🏻‍♀️

Both for my own stuff, and for the typical drive-by bazaar-contributions I do, this work well.

There are a lot of v1 editions of the age spec:

A manual-submission–only torrent collection that uses git. More robust than a crawler in some ways but doesn’t seem have a lot.

Having a couple of different local copies of the repo is usually not needed but it makes a lot of things way more straight-forward. And that goes especially when you’re new to git and don’t know every command. You can clone a fresh copy and use your normal file management and file melding tools.

The whole idea of a DVCS is to have many repos. That’s what the D is—“decentralized”.

Whether or not recording conflicts semantically would make sense for git’s native backend:

A deep dive into the Gitflow Workflow. Learn if this Git workflow is right for you and your team with this comprehensive tutorial.

“Notwithstanding any other terms in this License, this License is not available to You if You and/or your employer develop, produce, sell, and/or resell a product which contains substantially similar capabil- ities of the BitKeeper Software, or, in the reason- able opinion of BitMover, competes with the BitKeeper Software.” 🤦🏻‍♀️

So glad the BitKeeper days are over

Hydroxide is a third-party, open-source ProtonMail bridge.