+ [2014-09-03T21:27:51Z] miczac well, apparently git blame points me to a merge. I can see the line in question in git-blame's output, great, but I can't see it in the merged branch - using gitk.
+ [2014-09-03T21:36:50Z] miczac I found it by poking around in the output of 'git blame <file>|less', because I knew what to look for ... but this output is not chronological, there's a better way, no?
+ [2014-09-03T22:21:58Z] VxJasonxV no, the output isn't chronological, it's file line .... ogical
+ [2014-09-03T22:23:07Z] thibaultcha I don't know if there is another way honestl y.
+ [2014-09-03T22:27:53Z] miczac I couldn't find the commit in with gitk, but I found it in the online repo.

message no. 45398

Posted by miczac in #github at 2014-09-03T21:27:51Z

well, apparently git blame points me to a merge. I can see the line in question in git-blame's output, great, but I can't see it in the merged branch - using gitk.
+ [2014-09-04T01:48:55Z] Nena_Garcia algun chico para charlar
+ [2014-09-04T05:44:12Z] sunnyboywithsurf how do i merge changes from a master repository into my fork via cmd?
+ [2014-09-04T05:46:50Z] Seveas !sync
+ [2014-09-04T05:46:50Z] gitinfo [!fork_sync] You can read a nice guide on how to update your fork with the upstream repository here: https://help.github.com/articles/syncing-a-fork