Mercurial > evolve
changeset 6887:45cbf0af48e7 stable
tests: update old changeset hashes in test-tutorial.t
They actually should've been updated in 32ed5b6fadd3, but better late than
never.
Unfortunately, these messages are not tied directly to any command output, so
the issue with using nonexistent hashes was not immediately obvious after
running this test.
| author | Anton Shestakov <av6@dwimlabs.net> |
|---|---|
| date | Thu, 03 Oct 2024 09:34:56 +0400 |
| parents | 2540c03e1bf2 |
| children | 7ec9f4b04519 |
| files | tests/test-tutorial.t |
| diffstat | 1 files changed, 4 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/tests/test-tutorial.t Wed Oct 02 21:00:16 2024 +0400 +++ b/tests/test-tutorial.t Thu Oct 03 09:34:56 2024 +0400 @@ -1345,10 +1345,10 @@ } #endif -The older version 75954b8cd933 never ceased to exist in the local repo. It was +The older version 39b19dc3d1e4 never ceased to exist in the local repo. It was just hidden and excluded from pull and push. -.. note:: In hgview there is a nice dotted relation highlighting a44c85f957d3 as a new version of 75954b8cd933. This is not yet ported to ``hg log -G``. +.. note:: In hgview there is a nice dotted relation highlighting 5486682f4225 as a new version of 39b19dc3d1e4. This is not yet ported to ``hg log -G``. There is now an **unstable** changeset in this history. Mercurial will refuse to share it with the outside: @@ -1361,8 +1361,8 @@ [255] -To resolve this unstable state, you need to rebase bf1b0d202029 onto -a44c85f957d3. The `hg evolve` command will do this for you. +To resolve this unstable state, you need to rebase 0609f95eccab onto +5486682f4225. The `hg evolve` command will do this for you. It has a --dry-run option to only suggest the next move.