comparison mercurial/debugcommands.py @ 42894:38392d5bde8e

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
comparison
equal deleted inserted replaced
42893:34a46d48d24e 42894:38392d5bde8e
1764 parents = repo.unfiltered()[prec].parents() 1764 parents = repo.unfiltered()[prec].parents()
1765 parents = tuple(p.node() for p in parents) 1765 parents = tuple(p.node() for p in parents)
1766 repo.obsstore.create(tr, prec, succs, opts['flags'], 1766 repo.obsstore.create(tr, prec, succs, opts['flags'],
1767 parents=parents, date=date, 1767 parents=parents, date=date,
1768 metadata=metadata, ui=ui) 1768 metadata=metadata, ui=ui)
1769 repo.ui.status(('1 new obsolescence markers\n'))
1770 tr.close() 1769 tr.close()
1771 except ValueError as exc: 1770 except ValueError as exc:
1772 raise error.Abort(_('bad obsmarker input: %s') % 1771 raise error.Abort(_('bad obsmarker input: %s') %
1773 pycompat.bytestr(exc)) 1772 pycompat.bytestr(exc))
1774 finally: 1773 finally: