##// 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:

r12156:4c94b6d0 default
r43164:38392d5b default
Show More
test-backwards-remove.t
16 lines | 280 B | text/troff | Tads3Lexer
/ tests / test-backwards-remove.t
Martin Geisler
tests: unify test-backwards-remove
r11857 $ hg init
$ echo This is file a1 > a
$ hg add a
Martin Geisler
tests: remove unneeded -d flags...
r12156 $ hg commit -m "commit #0"
Martin Geisler
tests: unify test-backwards-remove
r11857 $ ls
a
$ echo This is file b1 > b
$ hg add b
Martin Geisler
tests: remove unneeded -d flags...
r12156 $ hg commit -m "commit #1"
Martin Geisler
tests: unify test-backwards-remove
r11857 $ hg co 0
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
B should disappear
$ ls
a