also sprach Joey Hess <jo...@debian.org> [2014-09-09 21:06 +0200]: > If ~/.mrconfig does not chain to ~/some/path/.mrconfig, > then mr is left looking for the first .mrconfig file it > can find at or under the current directory. So, when run in > /some/path/subdir/, it finds that .mrconfig, and ~/.mrconfig, but not > any other .mrconfigs you may have scattered around, and behaves as you > describe. > > The solution, then, is to use chaining from ~/.mrconfig ...
Is there a reason why it shouldn't backtrack up the tree? > Perhaps, then, it's best to leave this to the mr user to decide. > It's easy enough to configure mr to not update in one of the duplicates > if desired. For example, after noticing I had this problem in my > configuration, > I now have: > > [d-i] > checkout = svn co svn+ssh://jo...@svn.debian.org/svn/d-i/trunk d-i > chain = true > update = : # handled by d-i's mrconfig Nice! So saying something like chain=pure is really the same, except it would handle status/log/diff etc. as well, and implicitly. Maybe there is also a better way to do it, e.g. chain=true and then something like skip_all_but_checkout=true. -- .''`. martin f. krafft <madduck@d.o> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems "i must get out of these wet clothes and into a dry martini." -- alexander woolcott
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
