Comment by namdnay
10 years ago
Regarding 2 - Do you mean the destination repo has uncommitted changes? There is no need to nuke them, as pushing to this repo will have no influence on the working set: it will just add new changesets in the history!
10 years ago
Regarding 2 - Do you mean the destination repo has uncommitted changes? There is no need to nuke them, as pushing to this repo will have no influence on the working set: it will just add new changesets in the history!
OK, that makes sense. I imagined that hg implicitly updates remote working set and that parent complained about git's behavior because
worked as lazy man's single command deployment for him :)