This kind of change might be made if a user is switching to repositories, but the previous published locations make it difficult to use a shared repository. If the redirection is not taken into account when downloading the branch, no repository data will be seen at all.
I guess the above example can be simplified even further as a redirect of the form: oldserver/ oldlocation => http:// newserver/ repo/newlocatio n
http://
This kind of change might be made if a user is switching to repositories, but the previous published locations make it difficult to use a shared repository. If the redirection is not taken into account when downloading the branch, no repository data will be seen at all.