+ [2014-08-28T03:46:03Z] VxJasonxV just seemed unusually quiet
+ [2014-08-28T03:46:26Z] VxJasonxV it was at first, my SSH session had timed out remotely
+ [2014-08-28T03:47:06Z] VxJasonxV so the fact that it looked identical after reconnecting still felt stuck
+ [2014-08-28T03:47:29Z] VxJasonxV knew it wasn't as soon as I said something obviously
+ [2014-08-28T04:19:20Z] avi__ Hi, I'm studying the topics of issue trackers and I need some githubers to try out my NLP github issue tracker survey (10 minutes) to see if this NLP is actually relevant to software engineering. If you're interested just pm me and I'll send you the survey.

message no. 43656

Posted by avi__ in #github at 2014-08-28T04:19:20Z

Hi, I'm studying the topics of issue trackers and I need some githubers to try out my NLP github issue tracker survey (10 minutes) to see if this NLP is actually relevant to software engineering. If you're interested just pm me and I'll send you the survey.
+ [2014-08-29T06:59:45Z] Jason milki: being the twat that i am, i just committed track data from my credit card. woo!
+ [2014-08-29T06:59:53Z] Jason note to self: git add * is bad.
+ [2014-08-29T08:26:00Z] Mr`Jim I have created a feature branch from my working branch, committed and pushed a single file change and then gone onto the website to create a pull request. I have realised I should have created by feature branch from the upstream branch (as right now it is based on my working which has lots of other changes in). Can I fix this?
+ [2014-08-29T08:26:42Z] Mr`Jim Essentially I want to 'reset' (wrong word) my feature branch to the upstream version, then cherry pick my one fill commit, and then commit + push + create pull request.
+ [2014-08-29T08:28:27Z] tobiasvl can your feature branch be fast-forwarded to upstream?