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

releasing version 0.48
[code/myrepos.git] / TODO
1 * For compatability, ~/.mrtrust has to exist before trust checks are
2   enabled. Change this in a flag day.
3
4 * After the mtrust flag day, consider making something similar to -p 
5   be enabled by default. 
6
7   It should not be identical to -p, for the following reason: -p causes
8   mr to only look at the mrconfig it finds in the path (like -c only looks
9   at the specified file). But by default, mr should certianly load the
10   ~/.mrconfig (and files it chains). This allows a user to globally
11   configure mr with aliases, etc. (Closes: #557963)
12
13 * more revision control systems
14
15 * a way to detect repos in a tree that are not registered, and warn
16   about or even auto-register them. (svn externals make this quite
17   difficult!)
18
19 * When there are chained mrconfig files, mr could be smarter about
20   checkouts and updates. Ie, when a new version of an mrconfig file is
21   checked out or updated, throw all the info from the old one away, and
22   process the new one.
23
24   Until this is fixed, checkouts and updates need to be manually repeated
25   after mrconfig files have changes. (See #447553)