+ [2015-03-26T22:32:22Z] Seveas if they're 4 separate apps, make 4 repos
+ [2015-03-26T22:32:39Z] jgravois can I still do that?
+ [2015-03-26T22:33:18Z] Seveas sure
+ [2015-03-26T22:33:53Z] Seveas copy the repo 3 times, and filter-branch out each app
+ [2015-03-26T22:34:13Z] jgravois OK, I'll try that ... thanks

message no. 86110

Posted by nettlejam in #github at 2015-03-26T15:19:27Z

Trying this question again: Is there some git or github 'native' way to 'flag' a particular commit as you make it for later review? Like if the commit changes something about the code that should be documented? I'm new to git and my ignorant solution would be to maintain a text file somewhere else with notes, saying: watch out for commit abcdef0, it introduces a new required parameter, or something...
+ [2015-03-27T02:18:32Z] gh-status [Yellow] Minor service outage.
+ [2015-03-27T02:22:02Z] gh-status [Yellow] We are investigating increased error rates as an incoming DDoS amplifies their attack.
+ [2015-03-27T02:53:08Z] haasn I'm working on https://github.com/haasn/mpv/wiki/Upscaling and want to make it so that if you click on one of the images (eg. the rose), you get directed to that wiki page
+ [2015-03-27T02:53:22Z] haasn Right now I have the link like this: [image](upscaling/Rose.md) but that just links me to the raw page
+ [2015-03-27T02:53:31Z] haasn What's the proper way to do this?