backout: remove unnecessary frobbing of addremove option
authorKevin Bullock <kbullock@ringworld.org>
Tue, 12 Feb 2013 15:47:30 +0000
changeset 18686 0bca4d31f647
parent 18685 fafdff7e9c43
child 18687 1d183b33f007
backout: remove unnecessary frobbing of addremove option There's no way for addremove to show up in backout's opts dictionary. It was being set manually because cmdutil.commit expected it to be there (and would throw an exception if it wasn't). This was fixed waaaaaaay back in: changeset: 5829:784073457a0f user: Kirill Smelkov <kirr@mns.spb.ru> date: Thu Jan 10 12:07:18 2008 +0300 summary: cmdutil.commit: extract 'addremove' from opts carefully
mercurial/commands.py
--- a/mercurial/commands.py	Tue Feb 12 15:07:17 2013 +0000
+++ b/mercurial/commands.py	Tue Feb 12 15:47:30 2013 +0000
@@ -468,7 +468,6 @@
                 ui.setconfig('ui', 'forcemerge', '')
 
         commit_opts = opts.copy()
-        commit_opts['addremove'] = False
         if not commit_opts['message'] and not commit_opts['logfile']:
             # we don't translate commit messages
             commit_opts['message'] = "Backed out changeset %s" % short(node)