{"push_id":766558786,"size":1,"distinct_size":1,"ref":"refs/heads/AddExecCmd","head":"6dec851287c1e6b2e10df2c08091e627d50a337d","before":"6db9bb23ea99810ee9979c00db1098eb87771072","commits":[{"sha":"6dec851287c1e6b2e10df2c08091e627d50a337d","author":{"email":"ff3bde741799c0eff815b83a54eda3fc494df54f@us.ibm.com","name":"Doug Davis"},"message":"Add a 'start' command\n\nWhen any non-global-flag parameter appears on the command line make sure\nthere's a \"command\" even in the 'start' (run) case to ensure its not\nambiguous as to what the arg is. For example, w/o this fix its not\nclear if\n   runc foo\nmeans 'foo' is the name of a config file or an unknown command.  Or worse,\nyou can't name a config file the same a ANY command, even future (yet to\nbe created) commands.\n\nWe should fix this now before we ship 1.0 and are forced to support this\nambiguous case for a long time.\n\nSigned-off-by: Doug Davis <dug@us.ibm.com>","distinct":true,"url":"https://api.github.com/repos/duglin/runc/commits/6dec851287c1e6b2e10df2c08091e627d50a337d"}]}