What is a fork, really, and how GitHub changed its meaning
@sir I'm glad to know that I'm not the only one who was confused by GitHub's use of that term.
@josealberto4444 imagine you want to pull in a hundred changes in one fell swoop, like the addition of a new kernel driver
@josealberto4444 how would you feel if your inbox was bombed with a hundred patches? Multiplied across all the subscribers of a mailing list. Flame flame flame
@josealberto4444 note that the branch which is being pulled was probably built out of patches. It's most often used as "this group finished some long term work in a separate team, and is ready to integrate it further upstream now"
@josealberto4444 also, when merging unrelated histories patches don't work. Say you develop a kernel module as a standalone project, to be compiled against the latest kernel headers and installed separately from the kernel. But one day you decide to usptream it - so you send a request-pull and Linus fetches your branch and uses git merge --allow-unrelated-histories and there it is. Not possible with patches
@josealberto4444 no, I mean that they were never related in the first place. Git can merge together two repos that have nothing to do with each other
@sir @josealberto4444 The original meaning of git's pull request is well explained here also: https://blog.ffwll.ch/2017/08/github-why-cant-host-the-kernel.html
cmpwn.com is a private Mastodon instance for friends of SirCmpwn.