Explain a remote rejection of a non-fast-forward

This came up on the mailing list; if the remote repository rejects
a non-fast-forward push we should clarify it was the remote that
rejected this and guide the administrator to the relevant setting
involved on the remote side.

Change-Id: I7e143d4946e39c1bb9f4c554cc5e4fe00cdbb768
Signed-off-by: Shawn O. Pearce <sop@google.com>
CC: Luciano Carvalho <lscarval@gmail.com>
1 file changed