X-Git-Url: https://git.madduck.net/code/myrepos.git/blobdiff_plain/f600a37726c5ac539ba213214fe5fb3bcf0cfcbd..4f4322be5574dcbb4f9e975b35300b34dd232368:/TODO diff --git a/TODO b/TODO index a2255db..bc5d00b 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,14 @@ -* more revision control systems +* For compatability, ~/.mrtrust has to exist before trust checks are + enabled. Change this in a flag day. + +* After the mtrust flag day, consider making something similar to -p + be enabled by default. + + It should not be identical to -p, for the following reason: -p causes + mr to only look at the mrconfig it finds in the path (like -c only looks + at the specified file). But by default, mr should certianly load the + ~/.mrconfig (and files it chains). This allows a user to globally + configure mr with aliases, etc. (Closes: #557963) * 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 @@ -10,23 +20,4 @@ process the new one. 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 ", - 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. + after mrconfig files have changes. (See #447553)