further thoughts

[code/myrepos.git] / TODO

diff --git a/TODO b/TODO
index 9eb4e900c1a44ffc9baf11893879a84f05cc6bb1..a2255dbbf739a9ab46b856cc5675a3dd0b821d09 100644 (file)
--- a/TODO
+++ b/TODO
@@ -12,7 +12,21 @@
   Until this is fixed, checkouts and updates need to be manually repeated
   after mrconfig files have changes.
 
   Until this is fixed, checkouts and updates need to be manually repeated
   after mrconfig files have changes.
 

-* Ability to run commands in paralell? (-j n)
+* offline support

 
 

-  If done right, this could make an update of a lot of repos faster. If
-  done wrong, it could suck mightily. ;-)
+  If I commit something to git while offline, it would be nice if mr could
+  have a way to push that change when I get online.
+
+  One approach would be to notice when mr commit fails, and queue the
+  commit up to be tried happen again when "mr retry" is run. This could
+  also notice other failing commands, such as "mr up".
+
+  Would it make sense to have to first run "mr offline", before mr starts
+  recording such failures? If so, "mr online" would be the thing to run
+  when getting back online, this would both retry queued commands, and stop
+  queuing new failures.
+
+  One annoying thing is that, if offline, dns timeouts can take a while in
+  certian situations. So, it might be good to have a "mr remember <command>",
+  to directly add a command for mr to run when coming online, without
+  the need to run the command and wait for it to fail.