a todo item based on one from madduck, plus my own experiences with chained updates

[code/myrepos.git] / TODO

diff --git a/TODO b/TODO
index 6621db6f90ed9718e838136757f22b7513b8360a..442ee43b51eb71ed900b1dfe28e9a1339ce8ecd6 100644 (file)
--- a/TODO
+++ b/TODO
@@ -10,20 +10,17 @@
   [src/bar]
   renamedfrom = src/foo/bar
 
-  (Support multple renames of a single repo?)
+  (How to support multple renames of a single repo? List multiple
+  renamedfrom dirs?)
 
-* mr register
+* 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!)
 
-  Idea is you check out a repo and then use mr register to add it to the
-  closest mrconfig file.
+* 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.
 
-  mr register would be implemented as a shell command that then calls
-  mr config with flags that make it actually 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.