##// END OF EJS Templates
transaction: issue "new obsmarkers" message at the end of the transaction...
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.

File last commit:

r29974:7109d5dd default
r43164:38392d5b default
Show More
test-strict.t
26 lines | 435 B | text/troff | Tads3Lexer
Nicolas Dumazet
tests: unify test-strict
r12097 $ hg init
$ echo a > a
$ hg ci -Ama
adding a
$ hg an a
0: a
Yuya Nishihara
commands: parse ui.strict config item as bool
r16591 $ hg --config ui.strict=False an a
0: a
Nicolas Dumazet
tests: unify test-strict
r12097 $ echo "[ui]" >> $HGRCPATH
$ echo "strict=True" >> $HGRCPATH
$ hg an a
hg: unknown command 'an'
Martin von Zweigbergk
dispatch: don't show list of commands on bogus command...
r38823 (use 'hg help' for a list of commands)
Matt Mackall
tests: add exit codes to unified tests
r12316 [255]
Nicolas Dumazet
tests: unify test-strict
r12097 $ hg annotate a
0: a
should succeed - up is an alias, not an abbreviation
$ hg up
0 files updated, 0 files merged, 0 files removed, 0 files unresolved