Of course, usually you don't care. You know what you want and you know where it is. But if you were trying to import into another version control system (say because you find it easier to use), you might. There's a nice tool called
tailorwhich does this. So you might decide to use it. It works by getting the changesets from the old (say SVN) repository and then applying them in the new repository. But the changesets have paths relative to the repository root. That means that
tailorhas to strip off the "module" part of the paths, and for that
tailormust know which part of the URL is the module part.
It has a very simplistic way of doing this. You have to tell it which part is which. To check you, it will test to make sure the repository root you give it is actually valid. Now, a webserver I encountered last night wasn't properly configured, and as a result
tailorthought that test failed. At this point it bails, and tells me I screwed up.
That is, it bails unless you put the option "
trust-root = True" in the config file. That option tells
tailorto trust that I have given it the correct repository root. Unfortunately this option is documented neither in the command line help nor in the man page.
Aren't undocumented options grand!