X-Git-Url: https://git.madduck.net/code/myrepos.git/blobdiff_plain/59439878f5a85ff5ab6846106079549f3325d8ae..baeacba4762f92a24f888a0dab625e041e247184:/TODO?ds=inline

diff --git a/TODO b/TODO
index 86eaf5a..6358728 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,15 @@
+* For compatability, ~/.mrtrust has to exist before trust checks are
+  enabled. Change this in a flag day.
+
+* After the mtrust flag day, consider making something similar to -p 
+  be enabled by default. 
+
+  It should not be identical to -p, for the following reason: -p causes
+  mr to only look at the mrconfig it finds in the path (like -c only looks
+  at the specified file). But by default, mr should certianly load the
+  ~/.mrconfig (and files it chains). This allows a user to globally
+  configure mr with aliases, etc. (Closes: #557963)
+
 * more revision control systems
 
 * a way to detect repos in a tree that are not registered, and warn
@@ -10,18 +22,4 @@
   process the new one.
 
   Until this is fixed, checkouts and updates need to be manually repeated
-  after mrconfig files have changes.
-
-* offline support
-
-  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.
+  after mrconfig files have changes. (See #447553)