From 64271f903c43d7cf81603dd0d3ef5455f2c74b47 Mon Sep 17 00:00:00 2001 From: Matěj Cepl Date: Mon, 22 Jun 2015 08:31:08 +0200 Subject: Current state --- _posts/linus-on-github.rst | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 _posts/linus-on-github.rst (limited to '_posts/linus-on-github.rst') diff --git a/_posts/linus-on-github.rst b/_posts/linus-on-github.rst new file mode 100644 index 0000000..17922ca --- /dev/null +++ b/_posts/linus-on-github.rst @@ -0,0 +1,29 @@ +title: Linus on github +categories: + - computer +date: 2012-06-14T06:35:10 +tags: +--- + +Just to record for myself link to `the awesome discussion about +deficiencies of github`_. I have been tempted lately to the sweet +proprietary arms of github lately (yes, their cheap commenting threads +are a killer feature and as awesome as cheap branches in git itself). It +also leads to `the very nice blogpost on git commit messages`_. + +It is unfortunately very rare to get a good comparison between GitHub +and gitweb+git based on their technical merit, so the proprietary nature +of github then stands as the only problem of github. + +I should also take a longer look at ``git request-pull (1)``. Apparently +its documentation is its weakest part (see `example result`_ and +`Linus’s comment on what consitutes a good pull request`_). + +.. _`the awesome discussion about deficiencies of github`: + https://github.com/torvalds/linux/pull/17#issuecomment-5654674 +.. _`the very nice blogpost on git commit messages`: + http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html +.. _`example result`: + http://groups.google.com/group/linux.kernel/browse_thread/thread/c3de7bbe9bb73cf5/1d61f01ea9ec3c67?show_docid=1d61f01ea9ec3c67&pli=1 +.. _`Linus’s comment on what consitutes a good pull request`: + https://github.com/torvalds/linux/pull/17#issuecomment-5663780 -- cgit