@sir I'm glad to know that I'm not the only one who was confused by GitHub's use of that term.

@sir How can a patch be insufficient? (I'm talking about the PS of the article.)

We need git-request-pull.io 😂

@josealberto4444 imagine you want to pull in a hundred changes in one fell swoop, like the addition of a new kernel driver

@sir I see... But it is just a matter of simplifying the process, you could send a hundred patches, couldn't you? The result would be the same?

@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

@sir With unrelated you mean that they have diverged (but they could be merged without conflicts)?

@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 Oh... 🤯 I had no idea about that. I understand now, thanks!
@sir Facebook uses the RSS icon for subscribing to feeds, even though they don't support RSS
Sign in to participate in the conversation
Mastodon

cmpwn.com is a private Mastodon instance for friends of SirCmpwn.