+[2014-08-28T03:46:03Z]VxJasonxVjust seemed unusually quiet +[2014-08-28T03:46:26Z]VxJasonxVit was at first, my SSH session had timed out remotely +[2014-08-28T03:47:06Z]VxJasonxVso the fact that it looked identical after reconnecting still felt stuck +[2014-08-28T03:47:29Z]VxJasonxVknew 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.
I thought for sure I was scrolled back and behind, but couldn't scroll down.
+[2014-08-29T06:59:45Z]Jasonmilki: being the twat that i am, i just committed track data from my credit card. woo! +[2014-08-29T06:59:53Z]Jasonnote to self: git add * is bad. +[2014-08-29T08:26:00Z]Mr`JimI 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`JimEssentially 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]tobiasvlcan your feature branch be fast-forwarded to upstream?