And here are the upstream agit docs:

git remote set-url origin --push --add user1@repo1
git remote set-url origin --push --add user2@repo2
git remote -v

Then git push will push to user1@repo1, then push to user2@repo2.

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: