releasing version 0.51

[code/myrepos.git] / TODO

diff --git a/TODO b/TODO
index 2ed4be313918910f81417e5b090d4a2c5c3ff517..bc5d00bf90855edb9437c9fbf78ceb6a33f36049 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,16 +1,23 @@
-* more revision control systems
+* For compatability, ~/.mrtrust has to exist before trust checks are
+  enabled. Change this in a flag day.

 
 

-* support for tracking repo renames
+* After the mtrust flag day, consider making something similar to -p 
+  be enabled by default. 

 
 

-  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.
+  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)

 
 

-  [src/bar]
-  renamedfrom = src/foo/bar
+* 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
+  difficult!)

 
 

-  (Support multple renames of a single repo?)
+* When there are chained mrconfig files, mr could be smarter about
+  checkouts and updates. Ie, when a new version of an mrconfig file is
+  checked out or updated, throw all the info from the old one away, and
+  process the new one.

 
 

-* a way to detect repos in a tree that are not registered, and warn
-  about or even auto-register them
+  Until this is fixed, checkouts and updates need to be manually repeated
+  after mrconfig files have changes. (See #447553)