Why does Git remember and use a conflict resolution from an aborted rebase without asking me? -
i did rebase on branch foo
git rebase master
did conflict resolutions, decided didn't want it, , aborted.
git rebase --abort
all branch log histories normal. want start same process again.
git rebase master
when git hits first conflict hit first time, lists files in conflict did before. instead of marking conflict <<<<<
etc, shows file in state after resolved conflict first time. interesting has feature… want resolve 1 of conflicts differently, don't want remember , re-apply.
what going on here, , can turn off?
you can use rerere's "forget" function erase remembered conflict resolution.
Comments
Post a Comment