From 3a851213ad440476a37d2a318c4371b9e2c34ce2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 19 Jun 2016 14:01:33 -0400 Subject: fix filename --- .../comment_6_d0328983a68958a914bd9fc9fe5a3abe._comment | 13 +++++++++++++ .../comment_1_f42f2893433c312821d8d47f84cb5c43._comment | 13 ------------- 2 files changed, 13 insertions(+), 13 deletions(-) create mode 100644 doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe._comment delete mode 100644 doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe/comment_1_f42f2893433c312821d8d47f84cb5c43._comment (limited to 'doc/todo/integrate_shell-monad') diff --git a/doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe._comment b/doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe._comment new file mode 100644 index 00000000..8ba13e99 --- /dev/null +++ b/doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-06-16T21:04:55Z" + content=""" +Could use a tuple of a Data.Unique for the current build of propellor, +and a propellor build ID (eg, git rev that was built). + +That would make sure that propellor runs the correct IO action. +But, when propellor is updated, any cron jobs etc that try to run +with the old UniqueId would fail. Unless the old propellor binary +could be cached away and used as a fallback, I suppose.. +"""]] diff --git a/doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe/comment_1_f42f2893433c312821d8d47f84cb5c43._comment b/doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe/comment_1_f42f2893433c312821d8d47f84cb5c43._comment deleted file mode 100644 index 8ba13e99..00000000 --- a/doc/todo/integrate_shell-monad/comment_6_d0328983a68958a914bd9fc9fe5a3abe/comment_1_f42f2893433c312821d8d47f84cb5c43._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2016-06-16T21:04:55Z" - content=""" -Could use a tuple of a Data.Unique for the current build of propellor, -and a propellor build ID (eg, git rev that was built). - -That would make sure that propellor runs the correct IO action. -But, when propellor is updated, any cron jobs etc that try to run -with the old UniqueId would fail. Unless the old propellor binary -could be cached away and used as a fallback, I suppose.. -"""]] -- cgit v1.2.3