]> git.madduck.net Git - code/myrepos.git/commitdiff

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:

add
authorJoey Hess <joey@kitenet.net>
Fri, 5 Jul 2013 18:28:05 +0000 (14:28 -0400)
committerJoey Hess <joey@kitenet.net>
Fri, 5 Jul 2013 18:28:05 +0000 (14:28 -0400)
TODO
doc/todo/smarter_chained_checkout.mdwn [new file with mode: 0644]

diff --git a/TODO b/TODO
index 34ba317a16ebb373a3b654cef773133a07340c33..0cd761d7773d19513d16b77c08355083389a0ecb 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,11 +1,3 @@
 * 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. (See #447553)
diff --git a/doc/todo/smarter_chained_checkout.mdwn b/doc/todo/smarter_chained_checkout.mdwn
new file mode 100644 (file)
index 0000000..13e5d5a
--- /dev/null
@@ -0,0 +1,7 @@
+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. (See #447553)