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

442ee43b51eb71ed900b1dfe28e9a1339ce8ecd6
[code/myrepos.git] / TODO
1 * more revision control systems
2
3 * support for tracking repo renames
4
5   It should be possible to tell mr that there used to be a repo at
6   src/foo/bar, and it's been moved to src/bar. mr would then detect if the
7   move needs to be done, and handle it. This is mostly useful when mrconfig
8   files are shared accross several systems.
9
10   [src/bar]
11   renamedfrom = src/foo/bar
12
13   (How to support multple renames of a single repo? List multiple
14   renamedfrom dirs?)
15
16 * a way to detect repos in a tree that are not registered, and warn
17   about or even auto-register them. (svn externals make this quite
18   difficult!)
19
20 * When there are chained mrconfig files, mr could be smarter about
21   checkouts and updates. Ie, when a new version of an mrconfig file is
22   checked out or updated, throw all the info from the old one away, and
23   process the new one.
24
25   Until this is fixed, checkouts and updates need to be manually repeated
26   after mrconfig files have changes.