See 56d3e0b499df for the source of adding originalwd to the list of things that
cause wdir to be updated. That change didn't come with tests, and attempts to
recreate the scenario described have thus far failed.
Details
- Reviewers
martinvonz durin42 - Group Reviewers
hg-reviewers - Commits
- rHG1f114c797961: rebase: avoid clobbering wdir() with --dry-run or --confirm (issue6291)
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
I'm not real familiar with how rebase works, and seems like it's pretty intricate code. I'd also feel better if there were tests for the original commit referenced. But it's very unlikely that I'll have any time before the weekend to look at this again, so I thought I'd send it out now. Maybe it's narrow enough or maybe somebody can backfill the tests, and we can avoid a known data shredder in the next release.
tests/test-rebase-named-branches.t | ||
---|---|---|
342–344 | It seems to me that it also shouldn't affect a dirty working directory that is *related* to the source or destination. Right? |
tests/test-rebase-named-branches.t | ||
---|---|---|
342–344 | 56d3e0b499df seems to imply "yes", unless I'm either misunderstanding or your recent cleanups around rebases in progress changed that. |
It seems to me that it also shouldn't affect a dirty working directory that is *related* to the source or destination. Right?