Linus Torvalds won't do github pull requests

That's pretty relevant comment. GitHub pull request system is great if you want to attract a bunch of script kiddies to participate on your project. For serious work, not so much.

I also do not care for the pull requests, for much the same reasons. I like there is a way to bring a branch to a maintainer's attention and updating its commit range in event of updates before it is accepted, but the way messages that result from merging in the code is irritating, so I end up just using "git pull" to do the trick once the branch looks good to me.

Considering Linus created git, if I were running github I'd tend to listen to whatever he had to say about it...

I would say the same about github's forks-as-top-level-entities system.

Forking a project is a huge deal. Forking a git repository is no big deal.

Github does the former, and it encourages too-broad forks, and at the same time, discourages coordination and contribution with the original project. Nearly all forks should be short-lived and completely subsidiary to the main project.

I did all of LoseThos myself. No GPL code. At one point I had a Linux floppy routine. I got ATA info. Linux is copyrighted, not patented. There are no issues.

The state tries to sabatogage legitimate alternatives. The state will lose. You will receive severe judgement from God.

----

God says... C:\Text\HUCKFINN.TXT

looky here; you stop that putting on frills. I won't have it. I'll lay for you, my smarty; and if I catch you about that school I'll tan you good. First you know you'll get religion, too. I never see such a son."

He took up a little blue and yaller picture of some cows and a boy, and says:

"What's this?"

"It's something they give me for learning my lessons good."

He tore it up, and says:

"I'll give you something better--I'll give you a cowhide."

He set there a-mumbling and a-growli

----

I wrote a compiler and kernel. Linus just did a kernel. (But a fancy kernel.)