]> git.madduck.net Git - code/myrepos.git/blob - 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:

todo item about offline support
[code/myrepos.git] / TODO
1 * more revision control systems
2
3 * a way to detect repos in a tree that are not registered, and warn
4   about or even auto-register them. (svn externals make this quite
5   difficult!)
6
7 * When there are chained mrconfig files, mr could be smarter about
8   checkouts and updates. Ie, when a new version of an mrconfig file is
9   checked out or updated, throw all the info from the old one away, and
10   process the new one.
11
12   Until this is fixed, checkouts and updates need to be manually repeated
13   after mrconfig files have changes.
14
15 * offline support
16
17   If I commit something to git while offline, it would be nice if mr could
18   have a way to push that change when I get online.
19
20   One approach would be to notice when mr commit fails, and queue the
21   commit up to be tried happen again when "mr retry" is run. This could
22   also notice other failing commands, such as "mr up".
23
24   Would it make sense to have to first run "mr offline", before mr starts
25   recording such failures? If so, "mr online" would be the thing to run
26   when getting back online, this would both retry queued commands, and stop
27   queuing new failures.