Control: tags 645965 patch Hi,
It is not just mrconfig files in local git repo but manually generated ones and bootstrapped ones seems to suffer this problem of chain loading. This may be obvious for expert mr users but it is a bit non-obvious since it require us to fool mr with the shell command ":" (or "true") for update. I suggest to add an entry as attached patch. (Certainly, adding some special option to the "register" command indicating it is a local mrconfig is another way to address this type of issue. But I like to keep mr as simple as possible like now.) Osamu
>From a3acf52abcaff11a2fe21e6b8fc912334f404407 Mon Sep 17 00:00:00 2001 From: Osamu Aoki <[email protected]> Date: Sun, 16 Jun 2013 02:45:58 +0900 Subject: [PATCH] local mrconfig files --- mr | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/mr b/mr index 4d77368..eddd546 100755 --- a/mr +++ b/mr @@ -496,6 +496,20 @@ One mrconfig file should be listed per line. Either the full pathname should be listed, or the pathname can start with F<~/> to specify a file relative to your home directory. +=head1 LOCAL MRCONFIG FILES + +The chain loading of local mrconfig files which can not be updated from the +remote VCS is possible. For example, to chain load F<~/foo/bar/.mrconfig> from +F<~/.mrconfig>, place the following in F<~/.mrconfig>: + + [foo/bar] + update = : + chain = true + +and place the following in F<~/.mrtrust>: + + ~/foo/bar + =head1 OFFLINE LOG FILE The F<~/.mrlog> file contains commands that mr has remembered to run later, -- 1.7.10.4
