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.
Details
Details
- Reviewers
quark durin42 - Group Reviewers
hg-reviewers - Commits
- rHGecc96506c49d: obsmarker: track operation by default
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Comment Actions
I think we do need this information recorded. Previous discussion someone mentioned that 10% increase in obsstore size is bad. But the current obsstore format has other stupid repetitive information like "user". So I won't blame this patch.
Comment Actions
Did you activated it at Facebook? Do you have some number on the size with and without it?
Comment Actions
Facebook has been using it since Apr 2016: https://bitbucket.org/facebook/hg-experimental/commits/a4165c954c665e3c85a80127df4943dd31b78297
The obsstore size is usually way smaller than hg-committed so it's not a concern yet.
We have zero user with the feature disabled. You can calculate the size yourself since the size of a marker is known.