Details
- Reviewers
durin42 dlax - Group Reviewers
hg-reviewers - Commits
- rHGd901a88891fe: rebase: rerun a rebase on-disk if IMM merge conflicts arise
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
hgext/rebase.py | ||
---|---|---|
667 | Do we need to make another function? Can't we call rebase again with options modified? |
hgext/rebase.py | ||
---|---|---|
667 | Avoiding the recursion seems like a nice thing to me. I prefer what Phil has to just doing recursion... |
hgext/rebase.py | ||
---|---|---|
667 | Why would that be nice? Do you foresee any problem? Besides, now the rebase() no longer has a docstring, meaning that help is broken. |
hgext/rebase.py | ||
---|---|---|
667 | huh, weird. not sure how they did. |
I've moved the comment back to rebase() to fix the help issue. I'm mostly neutral on using recursion or using this approach, though I think having to pass a flag to prevent infinite recursion would be messy.
Do we need to make another function? Can't we call rebase again with options modified?