Add push to manpage synopsis. Closes: #603029

[code/myrepos.git] / TODO

diff --git a/TODO b/TODO
index 86eaf5a1deb933c6b02428619291b4b9479a9f9f..bc5d00bf90855edb9437c9fbf78ceb6a33f36049 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,14 @@
-* more revision control systems
+* 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)
 
 * a way to detect repos in a tree that are not registered, and warn
   about or even auto-register them. (svn externals make this quite
@@ -10,18 +20,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)