obsmarker: track operation by default
We added support for including the operation responsible for creating the obsmarker in 3546a771e376 (obsolete: add operation metadata to rebase/amend/histedit obsmarkers, 2017-05-09). However, soon thereafter, in f432897a9f49 (obsmarker: add an experimental flag controlling "operation" recording, 2017-05-20), it was hidden behind a config that was off by default. It seems unlikely that people will manually turn it on, and obsmarkers/evolution as a whole is still experimental anyway, so let's turn on the tracking by default. Differential Revision: https://phab.mercurial-scm.org/D722
Showing
- mercurial/configitems.py 1 addition, 1 deletionmercurial/configitems.py
- tests/test-drawdag.t 5 additions, 5 deletionstests/test-drawdag.t
- tests/test-histedit-obsolete.t 17 additions, 17 deletionstests/test-histedit-obsolete.t
- tests/test-obsmarker-template.t 8 additions, 8 deletionstests/test-obsmarker-template.t
- tests/test-obsolete-divergent.t 3 additions, 3 deletionstests/test-obsolete-divergent.t
- tests/test-obsolete.t 12 additions, 12 deletionstests/test-obsolete.t
- tests/test-rebase-obsolete.t 23 additions, 23 deletionstests/test-rebase-obsolete.t
- tests/test-strip.t 2 additions, 2 deletionstests/test-strip.t
Loading
Please register or sign in to comment