When things go wrong
Fetch and push have a couple of failure scenarios that require action on the part of the user or shared server administrator.
Access denial
If there are permissions or authentication problems for any of the reasons outlined in the section Configure security for fetching and pushing, the fetch or push will fail with a message from the shared server. The user or shared server administrator must then address the problem before the user can attempt the fetch or push again.
History does not fit
A fetch is only allowed if the files being fetched fit cleanly into the personal server, building precisely on a shared common history. If there are any conflicts or gaps, the fetch is rejected. Otherwise, the changelists from the shared server become new submitted changelists in the personal server.
If the fetch fails, this is probably because you have attempted to fetch revisions from the shared server to your personal server that are in conflict with revisions you’ve submitted to your personal server.
“Rewriting History” explains what to do to resolve this situation.
Note
As a best practice, you should generate a report of conflicts before
attempting a fetch, with the -n command-line option.