Ingo Molnar <mingo@elte.hu> writes:As long as the index *somehow* knows about these new files, they are removed. The situation is: (0) you start from a HEAD that does not have path xyzzy; (1) you attempt to merge a rev that has path xyzzy; (2) the merge conflicts, leaving higher staged index entries for the path. (3) you decide not to conclude the merge by saying "reset --hard". The old logic for "reset" was to remove paths that exist in the index at stage #0 (i.e. cleanly merged) and not in HEAD. The patch changes the rule to remove paths that exist in the index at any stage (i.e. including the ones that have conflicted and not resolved yet) and not in HEAD. -- 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
| Benjamin Herrenschmidt | Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway |
| Ulrich Drepper | Re: [patch 7/8] fdmap v2 - implement sys_socket2 |
| Washington Odhiambo | Weird Problem with NAT - more details |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
| David Miller | Re: [GIT]: Networking |
