]> git.madduck.net Git - code/myrepos.git/blobdiff - TODO

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

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 2ed4be313918910f81417e5b090d4a2c5c3ff517..442ee43b51eb71ed900b1dfe28e9a1339ce8ecd6 100644 (file)
--- a/TODO
+++ b/TODO
   [src/bar]
   renamedfrom = src/foo/bar
 
   [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?)
 
 * a way to detect repos in a tree that are not registered, and warn
 
 * a way to detect repos in a tree that are not registered, and warn
-  about or even auto-register them
+  about or even auto-register them. (svn externals make this quite
+  difficult!)
+
+* 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.
+
+  Until this is fixed, checkouts and updates need to be manually repeated
+  after mrconfig files have changes.