Jeff King wrote:I wanted to make the same special case that 'recount -i' has: Deleting everything does not "do nothing", but actually aborts the edit. So in rebase, deleting everything will not rebase anything (instead of rebasing "no patches" onto wherever you said). Along the same lines, in the above patch deleting everything does not patch "no changes", but aborts editing the hunk and leaves it unchanged. Do you think that behaviour confuses users? =46eeding it the single hunk would be enough, but doing it this way ensures that the edited hunk cannot step on another hunk's toes, i.e. produce a conflict that may prevent us from applying the patch at the end of the hunk selection loop. It's fairly unlikely of course, because the user would deliberately have to extend the hunk beyond its current borders by adding extra context from the original file. =2D-=20 Thomas Rast trast@student.ethz.ch
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| David Miller | Slow DOWN, please!!! |
| Masami Hiramatsu | Re: [RFC PATCH v4] Unified trace buffer |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Parag Warudkar | Re: 2.6.29-rc3: tg3 dead after resume |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
