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

projects / code / myrepos.git / blobdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | inline | side by side
use [.] instead of []
[code/myrepos.git] / TODO
diff --git a/TODO b/TODO
index a2255dbbf739a9ab46b856cc5675a3dd0b821d09..f5158cf47c9aa7a0521dbcf6976a8b7a86b1159c 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,3 +1,6 @@
+* For compatability, ~/.mrtrust has to exist before trust checks are
+  enabled. Change this in a flag day.
+
 * more revision control systems
 
 * a way to detect repos in a tree that are not registered, and warn
 * more revision control systems
 
 * a way to detect repos in a tree that are not registered, and warn
@@ -11,22 +14,3 @@
 
   Until this is fixed, checkouts and updates need to be manually repeated
   after mrconfig files have changes.
 
   Until this is fixed, checkouts and updates need to be manually repeated
   after mrconfig files have changes.
-
-* offline support
-
-  If I commit something to git while offline, it would be nice if mr could
-  have a way to push that change when I get online.
-
-  One approach would be to notice when mr commit fails, and queue the
-  commit up to be tried happen again when "mr retry" is run. This could
-  also notice other failing commands, such as "mr up".
-
-  Would it make sense to have to first run "mr offline", before mr starts
-  recording such failures? If so, "mr online" would be the thing to run
-  when getting back online, this would both retry queued commands, and stop
-  queuing new failures.
-
-  One annoying thing is that, if offline, dns timeouts can take a while in
-  certian situations. So, it might be good to have a "mr remember <command>",
-  to directly add a command for mr to run when coming online, without
-  the need to run the command and wait for it to fail.
hacking on myrepos

Legalese

All content available in this repository is copyright © martin f. krafft, unless otherwise noted.

All files and their content are released under the terms of the Artistic Licence 2.0, unless otherwise noted.

The operator of this repository shall not be held liable for offending content in pages linking to or linked from these page, nor does he endorse their content unless stated otherwise.