+ [2016-03-07T22:34:35Z] LeBlaaanc Whats the best way to get this into a "fork" (I guess?) https://github.com/facebook/react-native/commit/5c418655bf3423bff268aca670477a1ec8f5058e
+ [2016-03-07T22:34:53Z] LeBlaaanc I basically would like to apply that change on top of 0.21
+ [2016-03-07T22:34:57Z] LeBlaaanc (which is a tag
+ [2016-03-07T22:43:21Z] LeBlaaanc This is the best way I could figure out how to do this... https://github.com/buzznog/react-native
+ [2016-03-07T23:09:18Z] dgriffi how quickly does Github move on job applications?

message no. 126153

Posted by VxJasonxV in #github at 2016-03-07T01:05:51Z

qengho: I'm going to hazard a guess and say the API doesn't currently decide between public and private repo issues
+ [2016-03-08T01:20:38Z] hackal Hello, is there a way to have 2 keys (2 users) on one machine?
+ [2016-03-08T01:34:09Z] haasn Is there an upstream opinion on issue voting / “me too!” buttons?
+ [2016-03-08T01:35:15Z] haasn Maintaining an increasing number of bug reports and feature requests can make it very find a good priority. Tagging and sorting by comment volume can alleviate this to some degree but I think it would be useful if I could just “sort by popularity”
+ [2016-03-08T01:35:31Z] haasn To easily see which feature requests are widely desired and which are not
+ [2016-03-08T01:44:07Z] VxJasonxV haasn: GitHub used to have voting