To reproduce: - Rebase a branch "foo" on a branch "bar" in a way that there is a conflict that you have to manually resolve. - Run git diff and see the conflict - Edit the conflicted file and remove all the conflicting bits (that could be a valid resolution of the conflict) - Now git diff produces an empty diff - git add $CONFLICTED_FILE as you have resolve the conflict - git rebase --continue You get the following error: No changes - did you forget to use 'git add'? git status is empty as the conflict was resolved. A simple workaround is to add a dummy blank line in the conflicted file so the diff is not empty. G. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Michal Piotrowski | Re: 2.6.23-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Fred Tyler | Slow, persistent memory leak in 2.6.20 |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Antonio Almeida | HTB accuracy for high speed |
