The fix in 8ede973597fd (rebase: handle successor targets (issue5198),
2016-04-11) only fixed the case where p2's successor was in the
destination, and only when the successor was exactly the destination
(i.e. not when the successor was an ancestor of it). This patch adds a
test case for when p1's successor is in the destination. It adds
another one for when the successor is an ancestor of the
destination. To do that simply, it also rewrites the test case using
drawdag.
Details
Details
- Reviewers
quark - Group Reviewers
hg-reviewers - Commits
- rHG644dddccc265: tests: demonstrate broken rebase of merge with p1's successor in dest
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
Comment Actions
Looks great! Thanks for finding and documenting these tricky cases!
There are a few places that might miss some English words. Those could probably be fixed in flight.
tests/test-rebase-obsolete.t | ||
---|---|---|
960 | s/parent ancestor/parent being ancestor/g ? |
tests/test-rebase-obsolete.t | ||
---|---|---|
960 | Hmm, that didn't read very well (my version of it). I rephrased it slightly differently. |
s/parent ancestor/parent being ancestor/g ?