Mercurial > hg
view tests/test-issue612.t @ 47731:485ae37a7ec5
dirstate: enforce `possibly_dirty` in `set_tracked`
There is some usecase (like `hg revert`) that requires more agressive
`possibly_dirty` setting. So we take a safe path and enforce it in one of the
main `normallookup` replacement.
Differential Revision: https://phab.mercurial-scm.org/D11173
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Mon, 19 Jul 2021 14:02:58 +0200 |
parents | 4441705b7111 |
children | 55c6ebd11cb9 |
line wrap: on
line source
https://bz.mercurial-scm.org/612 $ hg init $ mkdir src $ echo a > src/a.c $ hg ci -Ama adding src/a.c $ hg mv src source moving src/a.c to source/a.c $ hg ci -Ammove $ hg co -C 0 1 files updated, 0 files merged, 1 files removed, 0 files unresolved $ echo new > src/a.c $ echo compiled > src/a.o $ hg ci -mupdate created new head $ hg status ? src/a.o $ hg merge merging src/a.c and source/a.c to source/a.c 0 files updated, 1 files merged, 0 files removed, 0 files unresolved (branch merge, don't forget to commit) $ hg status M source/a.c R src/a.c ? src/a.o