Hacker News new | ask | show | jobs
by dblock 2612 days ago
I used patches and lists before, a lot. It was either hard or impossible to track more than one at a time, in context and with lots of conversations around specific lines of code. It was also a nightmare for maintainers to constantly want to tell people to rebase their patches based on other people's patches. To link patches to other patches to issues, etcetera.

The Github website and its fork/pull request flow has increased my productivity and the amount of things I contribute to or can maintain with some level of sanity 100x easily.
1 comments
kazinator 2612 days ago
Patches sucked, so Torvalds switched to BitKeeper and then wrote Git.

If my project uses Git, I can easily accept a patch. If someone happens to give me a patch against some old version that doesn't apply to HEAD, I can just "git reset --hard" the HEAD that version, apply the patch, and then rebase with "git rebase".

I would expect most people to be making patches out of their own git repo (using "git format-patch") anyway; they should be able to rebase first.

link