X-Git-Url: https://git.madduck.net/code/myrepos.git/blobdiff_plain/53d1d56fd9100a36b53467ed049276ecc1f7a09e..47e02526e5c54c0723d4d0e1fe28368cd4a697f6:/TODO?ds=sidebyside diff --git a/TODO b/TODO index 62df27e..bc5d00b 100644 --- a/TODO +++ b/TODO @@ -1,38 +1,23 @@ -* more revision control systems -* support for tracking repo renames +* For compatability, ~/.mrtrust has to exist before trust checks are + enabled. Change this in a flag day. - It should be possible to tell mr that there used to be a repo at - src/foo/bar, and it's been moved to src/bar. mr would then detect if the - move needs to be done, and handle it. This is mostly useful when mrconfig - files are shared accross several systems. +* After the mtrust flag day, consider making something similar to -p + be enabled by default. - [src/bar] - renamedfrom = src/foo/bar + 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) - (Support multple renames of a single repo?) +* 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 + difficult!) -* repo deletions +* When there are chained mrconfig files, mr could be smarter about + checkouts and updates. Ie, when a new version of an mrconfig file is + checked out or updated, throw all the info from the old one away, and + process the new one. - Handling repo deletions might also be possible, but is tricky, since - there's no good way to tell if a local checkout of a given repo is clean - and really should be deleted. Probably better for mr to just warn that a - repo still exists on disk that it is no longer managed. - - [src/foo/baz] - deleted = yes - -* mr register - - Idea is you check out a repo and then use mr register to add it to the - closest mrconfig file. - - mr register would be implemented as a shell command that then calls - mr config with flags that make it actually edit the mrconfig file: - - if [ -d "$MR_REPO/.svn" ]; then - url=$(svn info "$MR_REPO" | grep -i ^URL: | cut -d ' ' -f 2) - if [ -z "$url" ]; then - error "cannot determine svn url" - fi - mr -c "$MR_CONFIG" config --add "$MR_REPO" --checkout="svn co $URL" - fi + Until this is fixed, checkouts and updates need to be manually repeated + after mrconfig files have changes. (See #447553)