{"push_id":707453627,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"b2ea9d5e665e73f3ea5dbc2d8ffcb1812c16e587","before":"314e60f4bf500f1e52fd9983a8bfd42a5ff4d68d","commits":[{"sha":"80a464d0969417bdfad6de73984de20261ee8241","author":{"email":"f75897670c17327c42ab201733fb8a81ff9f4c34@tremily.us","name":"W. Trevor King"},"message":"README: Focus on local runtime (create/start/stop)\n\nThese actions need consistent tooling, and they're the sweet spot for\ntools like runc.  Once you map the container spec to the filesystem,\nthe other actions (copy, snapshot, upload, download) can all be\nhandled by existing tools (e.g. POSIX's 'cp', 'btrfs subvolume\nsnapshot', netcat, etc.).  If existing tooling for those actions is\nnot sufficiently portable, new portable tools can be written, but that\nshould be separate from the container-specific stuff here.\n\nI'm not sure about the intended meaning of the 'tagged' action.  Was\nthat intended for discoverability (\"I want a container named 'Nginx'\")\nor auth (\"Is my local /srv/nginx the same container 'Nginx' that Bob\naudited?\").  I think both are independent of the container runtime\nthough.","distinct":true,"url":"https://api.github.com/repos/opencontainers/specs/commits/80a464d0969417bdfad6de73984de20261ee8241"},{"sha":"b2ea9d5e665e73f3ea5dbc2d8ffcb1812c16e587","author":{"email":"97c25b088010000db66b15087ff5e27bf23e97c4@me.com","name":"Mrunal Patel"},"message":"Merge pull request #21 from wking/drop-checkpoints\n\nREADME: Focus on local runtime (create/start/stop)","distinct":true,"url":"https://api.github.com/repos/opencontainers/specs/commits/b2ea9d5e665e73f3ea5dbc2d8ffcb1812c16e587"}]}