Colin Walters d49718a619 deploy: Bump the mtime on ostree/deploy after deployments finish
This allows other processes (e.g. rpm-ostreed) to monitor for external
changes (e.g. if someone does `ostree admin undeploy`) in a relatively
sane fashion.

Specifically, I'm trying to fix:
https://github.com/projectatomic/rpm-ostree/issues/220
2016-03-03 08:52:42 -05:00
..
2015-08-26 12:16:29 -07:00
2016-01-27 11:44:10 -05:00
2016-03-01 10:08:25 -05:00
2016-01-27 11:44:10 -05:00
2015-08-25 09:27:56 -04:00
2016-01-27 11:44:10 -05:00