obsmarker: add an experimental flag controlling "operation" recording
It seems better to introduce the experiment behind a flag for now as there are multiple concerns around the feature: * Storing operation increase the size of obsolescence markers significantly (+10-20%). * It performs poorly when exchanging markers (cannot combine command names, command name might be unknown remotely, etc)
Showing
- mercurial/obsolete.py 4 additions, 1 deletionmercurial/obsolete.py
- tests/test-histedit-obsolete.t 23 additions, 21 deletionstests/test-histedit-obsolete.t
- tests/test-obsolete.t 9 additions, 9 deletionstests/test-obsolete.t
- tests/test-rebase-obsolete.t 25 additions, 23 deletionstests/test-rebase-obsolete.t
Loading
Please register or sign in to comment