I really like the mailing-list-centric development style recommended by https://git.sr.ht, but the instructions about how to use git send-email instead of your normal MUA are confusing/misleading and have often lead to broken threads.

I think I'm sticking with the client that I've used for decades and behaves the way I want it to; better to have one or two patches borked here and there over never being able to continue a thread.

git.sr.ht

@technomancy Interesting. Do you think the instructions at git-send-email.io could be fixed, or are your problems inherent to git send-email?

@baberiel_d seems like a combination of both; the man page for git-send-email claims to be able to use in-reply-to, but when I tried it I couldn't get it to work as advertised; the docs are either wrong or hopelessly misleading.

so it could be git-send-email.io doesn't recommend it because it just doesn't work, or it could be because (I don't know; this seems baffling but it's possible) he actually thinks starting a new thread for revised patches is a good idea somehow?? not sure.

@technomancy @baberiel_d I'm going to dig into this a bit