It would previously delete and recreate git-cl-repo if it
saw that the remote was different than expected. This looks
like it was added for the transition from the old SVN repo
to the new git one, but it also has the effect of losing
any local changes that have been made in the repo. :-(
Everyone should be updated by now, so print a helpful error
and exit instead.
Review URL: http://codereview.chromium.org/609002
git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@39099 0039d316-1c4b-4281-b951-d872f2087c98
Otherwise, all the parameters are coagulated into a single one.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/119308
git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@17968 0039d316-1c4b-4281-b951-d872f2087c98
They automatically git clone the original repository and execute the original script. So if they are first in the path, they will be executed. If a user has another git-cl/try in the path prior, these stubs won't be used at all and won't mess with the user's setup.
Also fix a bug with git handling in trychange.py
Review URL: http://codereview.chromium.org/119244
git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/depot_tools@17737 0039d316-1c4b-4281-b951-d872f2087c98
derat@chromium.org
msb@chromium.org
maruel@chromium.org