Yann Dirson wrote: > OK. In that case, all directories should have to be ordered top-down, > in case one defines more such nested repos.
Don't worry, mr does so. :) BTW: j...@gnu:~/tmp/e>~/src/mr/mr bootstrap file:///home/joey/tmp/mrconfig mr checkout: /home/joey/tmp/e/. Initialized empty Git repository in /home/joey/tmp/e/.git/ mr checkout: /home/joey/tmp/e/foo Initialized empty Git repository in /home/joey/tmp/e/foo/.git/ mr checkout: /home/joey/tmp/e/foo/bar Initialized empty Git repository in /home/joey/tmp/e/foo/bar/.git/ Checking out files: 100% (168/168), done. mr bootstrap: finished (3 ok) > In this respect, it would be useful to document precisely what gets > used in the bootstrap mrconfig and what gets ignored. I suppose that > [DEFAULT] is also taken into account when resolving [.], but what > about includes ? It's no different from any other mrconfig file: If trust checking is enabled, the bootstrapped mrconfig will be untrusted, and none of that will be allowed. Otherwise it will all work as usual. -- see shy jo
signature.asc
Description: Digital signature
