Mercurial > public > mercurial-scm > hg-stable

diff mercurial/debugcommands.py @ 42900:38392d5bde8e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
transaction: issue "new obsmarkers" message at the end of the transaction Instead of making bundle2 code responsible for this, it seems better to have it handled and the transaction level. First, it means the message will be more consistently printed. Second it means we won't spam the message over and over if the data arrive in multiple piece. Third, we are planning to move other similar message at the same level (for the same reason) so having them all at the same location will help us to control the order they are displayed.
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Sun, 14 Oct 2018 12:59:02 +0200
parents 34a46d48d24e
children 34ed651ba7e4
line wrap: on
line diff
--- a/mercurial/debugcommands.py	Sun Oct 14 13:19:24 2018 +0200
+++ b/mercurial/debugcommands.py	Sun Oct 14 12:59:02 2018 +0200
@@ -1766,7 +1766,6 @@
                 repo.obsstore.create(tr, prec, succs, opts['flags'],
                                      parents=parents, date=date,
                                      metadata=metadata, ui=ui)
-                repo.ui.status(('1 new obsolescence markers\n'))
                 tr.close()
             except ValueError as exc:
                 raise error.Abort(_('bad obsmarker input: %s') %