Products · Pattern or everyday thing
Email patch workflow
Raised as a usability problem by 5 people on Hacker News over 8 years (2019–2026), in 5 threads.
People raised many different problems with Email patch workflow, but no single problem has yet been raised by 3 people in 3 different months and threads.
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 6 complaints
- Sending patches by email needs many manual setup steps and is easy to get wrong2026-08-18
- Patches don't name a base commit, so senders must carefully rebase first2023-08-11
- Reading patches with large font or on mobile is awful because hard wrapping forces short lines2020-06-01
- Hard to set up git format-patch and git send-email without clear documentation2020-05-31
- Difficult to send and apply patches via email; tooling is complex and incomplete2020-05-01
- Email-based contributions and issue tracking are a ton of bad UX, hard for many developers2019-05-29