News for hackers. Stuff that matters.
Re:Why SQLite Does Not Use Git by skybrian on Tuesday April 10, 2018 @06:52PM (#16806350)
This is fine when you're working on your own project.

However, if you want to send a patch to someone else's project on Github, you have to create a remote fork, download the fork, and push it to your remote fork, then send the pull request. (I have tried other ways but they don't seem to work.)

This is fairly annoying since it's extra steps and it clutters many people's Github accounts with forked versions of projects they contribute to. There's no good reason for these forks to exist.

But this is a problem with Github and not git itself.

Re:Why SQLite Does Not Use Git by kbsletten on Tuesday April 10, 2018 @06:57PM (#16806393)
On the other hand, do you really want random people on the internet to be able to inject objects into your git repository by creating a branch or whatever? Especially after SHAttered, that's a huge liability that sort-of justifies the "you take yours and go over there" approach.
Re:Why SQLite Does Not Use Git by skybrian on Wednesday April 11, 2018 @11:48PM (#16817822)
Of course not. You want to send them a patch and have it show up in their "inbox" on Github as a pull request. There's no reason to put pull requests into the git repo.