Details
- Reviewers
durin42 martinvonz marmoute pulkit - Group Reviewers
hg-reviewers - Commits
- rHGe429e7c801b2: error: normalize "unresolved conflicts" error messages with a custom class
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Can you separate the change from "unresolved conflicts (see hg resolve, then hg rebase --continue)" to "unresolved conflicts (see 'hg resolve', then 'hg rebase --continue')", to make the diff less noisy?
Of course, it feels stupid to change code that’s going to be replaced in the next patch. Still, I think it makes things easier to review (at least that’s my opinion, I don’t know if more experienced reviewers agree).
Done. Added a temporary legacy hook which is removed in D8730; all the .t file updates are moved to that revision as well.
Of course, it feels stupid to change code that’s going to be replaced in the next patch. Still, I think it makes things easier to review (at least that’s my opinion, I don’t know if more experienced reviewers agree).
I suppose it's nice in this case because it confirms that it's only the rebase message that's changing (whereas otherwise, you'd need to check every .t file to see this).
mercurial/error.py | ||
---|---|---|
117 | I think it would have been easier to have
Generally, patches should not depend on other patches applied later. "Depend" is a bit vague. If the tests fail in between, it’s of course a forbidden dependency. If the tests pass in between, it might be acceptable. Still, in this case, probably both patches should be committed at the same time. If you organize like I proposed above, the text change can be committed independently. Also the total length of both patches would be shorter. |
mercurial/error.py | ||
---|---|---|
117 | Done. |
unrelated change