News for hackers. Stuff that matters.

A comment on GitHub’s Large File Storage is no panacea for Open Source. Parent comment

Re:GitHub’s Large File Storage is no panacea for Open Source by Jasper_ on Saturday October 24, 2015 @05:58PM (#10445011)
They still use pull requests, though, just in the form of email-based ones.

https://git-scm.com/docs/git-request-pull

[ Parent | on HN ]
Re:GitHub’s Large File Storage is no panacea for Open Source by paulddraper on Saturday October 24, 2015 @08:08PM (#10445382)
Sure. With git-fu and enough emails, you can replicate anything done in GitHub.

I'm just saying it's a very odd choice for an example of GitHub screwing over workflows.

[ Parent | on HN ]
Re:GitHub’s Large File Storage is no panacea for Open Source by jumpwah on Saturday October 24, 2015 @06:33PM (#10445134)
Except that's not a "pull request".
[ Parent | on HN ]
Re:GitHub’s Large File Storage is no panacea for Open Source by Vendan on Saturday October 24, 2015 @06:49PM (#10445179)
Except it is. Just cause github does pull requests differently doesn't mean you can't do pull requests in pure git. Remember, git came before github.
[ Parent | on HN ]
Re:GitHub’s Large File Storage is no panacea for Open Source by jumpwah on Sunday October 25, 2015 @11:28PM (#10449466)
> Remember, git came before github.

That's exactly my point. Using a "request-pull" instead of a "pull-request" will probably mean you can do this git-lfs thing with it. My understanding was that it was not working with "forked" repositories, which you need to have to make a "pull request". To make a "request pull" (or to just send a patch file), you don't need to "fork". ;)

[ Parent | on HN ]