We had a report of a situation like this borking a user at Google, but
I can't reproduce it in a test. Let's at least backstop the issue with
a test, so we don't accidentally introduce such a bug...
Details
Details
- Reviewers
pulkit - Group Reviewers
hg-reviewers - Commits
- rHGbca57ad9e630: histedit: add test that an invalid editor doesn't bork client state
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage