We only have one place that calls ms.reset() with any
arguments. That place is mergestate.clean(). The callers that call
the function with no arguments seem to all just want delete the
mergestate -- none of them look at the instance after calling
reset(). Let's separate out the two different use cases to make the
code clearer. I'll clean up further soon.
Details
Details
- Reviewers
indygreg - Group Reviewers
hg-reviewers - Commits
- rHG08c6d6962b2a: mergestate: split up reset() for its two use cases
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
mercurial/mergestate.py | ||
---|---|---|
205 | It is slightly weird to me that reset() doesn't wipe out these attributes after this change. Shouldn't a reset... reset to default state (None)? |
It is slightly weird to me that reset() doesn't wipe out these attributes after this change. Shouldn't a reset... reset to default state (None)?