releasing version 1.10

[code/myrepos.git] / TODO

diff --git a/TODO b/TODO
index 000d5abbe7376caa7ed5efb0b745aaa530835df0..34ba317a16ebb373a3b654cef773133a07340c33 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,29 +1,11 @@
-* 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
+  difficult!)
 
-* support for tracking repo renames
+* 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.
 
-  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.
-
-  [src/bar]
-  renamedfrom = src/foo/bar
-
-  (Support multple renames of a single repo?)
-
-* mr register
-
-  Idea is you check out a repo and then use mr register to add it to the
-  closest mrconfig file.
-
-  mr register would be implemented as a shell command that then calls
-  mr config with flags that make it edit the mrconfig file:
-
-  if [ -d "$MR_REPO/.svn" ]; then
-       url=$(svn info "$MR_REPO" | grep -i ^URL: | cut -d ' ' -f 2)
-       if [ -z "$url" ]; then
-               error "cannot determine svn url"
-       fi
-       mr -c "$MR_CONFIG" config --add "$MR_REPO" --checkout="svn co $URL"
-  fi
+  Until this is fixed, checkouts and updates need to be manually repeated
+  after mrconfig files have changes. (See #447553)