Félix Sipma wrote: > [example] > checkout = git clone g...@example.com:example.git > > mr fails when running "mr update": > ~/builds$ mr update > mr: illegal checkout command "git clone g...@example.com:example.git" in > untrusted /home/user/builds/.mrconfig line 2
The problem is that your mrconfig file does not specify what directory to check out into. Git has a behavior that happens to make that check out into the directory named example, but mr is not aware of that. (And I don't really fancy making a security sensative part of mr try to track default checkout directories used by different version control systems.) If you configured mr to trust that mrconfig file (which you can easily do by listing the filename in ~/.mrtrust), it would happily run the checkout command as specified. There is not reason not to configure mr to trust your own mrconfig files. -- see shy jo
signature.asc
Description: Digital signature
