qimportbz: use ui.status() rather than ui.write() when appropriate (bug 980986)
authorEd Morley <emorley@mozilla.com>
Wed, 18 Mar 2015 14:00:14 +0000
changeset 360606 513b0c301a7c45b3997359b55a87c2e37b5b5fb4
parent 360605 4ca0f73b40c352df7e149daaaa38242b8697c297
child 360607 fecb1c2c6f5f98a231dc11edf70dfe3a97f6b21c
push id16998
push userrwood@mozilla.com
push dateMon, 02 May 2016 19:42:03 +0000
bugs980986
qimportbz: use ui.status() rather than ui.write() when appropriate (bug 980986)
hgext/qimportbz/__init__.py
--- a/hgext/qimportbz/__init__.py
+++ b/hgext/qimportbz/__init__.py
@@ -170,17 +170,17 @@ def extsetup(ui):
             if newpatchname != oldpatchname:
                 if newpatchname in q.series:
                     q.delete(repo, [newpatchname], {})
                 qrename(ui, repo, oldpatchname, newpatchname)
                 # mq always reports the original name, which is confusing so we'll
                 # report the rename. But if ui.verbose is on, qrename will have already
                 # reported it.
                 if not ui.verbose:
-                    ui.write("renamed %s -> %s\n" % (oldpatchname, newpatchname))
+                    ui.status("renamed %s -> %s\n" % (oldpatchname, newpatchname))
 
         # now process the delayed imports
 
         # these opts are invariant for all patches
         newopts = {}
         newopts.update(opts)
         newopts['force'] = True