]> 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:

de-hardcode paths
[code/myrepos.git] / TODO
diff --git a/TODO b/TODO
index 69fab7d66684c08c2bbf24ddbfe920cd513d2182..f5158cf47c9aa7a0521dbcf6976a8b7a86b1159c 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,18 +1,16 @@
-* more revision control systems
-
-* support for tracking repo renames
-
-  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
+* For compatability, ~/.mrtrust has to exist before trust checks are
+  enabled. Change this in a flag day.
 
 
-  (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
   difficult!)
 
 * 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!)
+
+* 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.