Fix handling of a repository in "."

[code/myrepos.git] / TODO

diff --git a/TODO b/TODO
index 401f9bf770507ea4cbd566efc3b48d3a3b9dffae..635872891be1d98ebcfdd6b41880d2f6526c87f5 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,17 +1,16 @@
-* more revision control systems
-
-* support for tracking repo renames
+* For compatability, ~/.mrtrust has to exist before trust checks are
+  enabled. Change this in a flag day.
 
-  It should be possible to tell mr that there used to be a repo at
-  src/foo/bar, and it's been moved to src/bar. mr would then detect if the
-  move needs to be done, and handle it. This is mostly useful when mrconfig
-  files are shared accross several systems.
+* After the mtrust flag day, consider making something similar to -p 
+  be enabled by default. 
 
-  [src/bar]
-  renamedfrom = src/foo/bar
+  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)
 
-  (How to support multple renames of a single repo? List multiple
-  renamedfrom dirs?)
+* more revision control systems
 
 * 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
@@ -23,9 +22,4 @@
   process the new one.
 
   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)
-
-  If done right, this could make an update of a lot of repos faster. If
-  done wrong, it could suck mightily. ;-)
+  after mrconfig files have changes. (See #447553)