{"ref":"refs/heads/mine","commits":[{"author":{"name":"Ran Benita","email":"03686f031484546e32da38cdd36b1b8bb5e2be3c@gmail.com"},"sha":"b76ebe6f5e2137aa3741dcaaa3e72c9ad4f2b845","message":"output: save and restore crtc upon (de)activation\n\nThe crtc is saved from kmscon_output_activate, and restored from\nkmscon_output_deactivate.\nThis means that when the program exits, the screen is back to what it\nwas - we don't need to switch back VTs if we started the program from an\nfbcon, etc.","url":"https://api.github.com/repos/bluetech/kmscon/commits/b76ebe6f5e2137aa3741dcaaa3e72c9ad4f2b845"},{"author":{"name":"Ran Benita","email":"03686f031484546e32da38cdd36b1b8bb5e2be3c@gmail.com"},"sha":"24fcc2b6364003e205dcfb9828629eb66f630ae2","message":"output: bind new modes in the order we add them\n\nCurrently, when a new mode is bound to an output, it is inserted at the\nhead of the list, i.e. reversed from the order they are present in the\ndrmModeConnector modes array. But it's better to keep the order, because\nit seems the best (high-res) modes come first; this way the lazy user,\nwho just passes NULL to kmscon_output_activate, would get a nice looking\ndefault mode.","url":"https://api.github.com/repos/bluetech/kmscon/commits/24fcc2b6364003e205dcfb9828629eb66f630ae2"}],"head":"24fcc2b6364003e205dcfb9828629eb66f630ae2","push_id":51706505,"size":2}