-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge_tools: create builtin merge editor #2118
Conversation
befefab
to
e932658
Compare
144b08d
to
a06f030
Compare
e932658
to
18b3d7a
Compare
a06f030
to
715b590
Compare
18b3d7a
to
b522168
Compare
715b590
to
a375859
Compare
a375859
to
ee77c67
Compare
d69c2f1
to
875c24f
Compare
875c24f
to
f5426d2
Compare
3e26b49
to
82f2e6b
Compare
f5426d2
to
c2dde80
Compare
82f2e6b
to
5dd2cfa
Compare
@arxanas, let me know which of your PRs are ready for review. This one seems to be at the bottom of the stack, but GitHub says it has changes conflicting with |
@martinvonz The PRs marked as ready for review are ready. The conflict warning in GitHub can be misleading — this stack actually rebases without introducing any conflicts. |
c2dde80
to
b604a2d
Compare
b604a2d
to
7446c53
Compare
7446c53
to
113e4fe
Compare
I have no idea why, but I had to force a rescan of the CLA using an internal web page. |
Checklist
If applicable:
CHANGELOG.md