Johannes Schindelin [off-list ref] writes:
On Wed, 31 Oct 2007, Sergei Organov wrote:
quoted
Yes, and that's the problem. Why 'git --continue' didn't just skip this
patch that *already became no-op* after conflict resolution and forced
me to explicitly use 'git --skip' instead?
Isn't that obvious? To prevent you from accidentally losing a commit.
The commit would not change anything, so what is there to lose?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum