On Monday 09 June 2008, Johannes Schindelin wrote:Is there a good reason against having *both*? AFAICS, there's nothing stopping us from having both a "-e"-option to git-add, and an "e"-command inside git-add--interactive. ...just like we have "-p" and "p" today... ("git-add -e" would open the entire diff in an editor, as would "e" from the *main* menu of git-add--interactive. However, "e" from the *single hunk* menu would of course open only that single hunk within the editor. We could even have an "E" command to open all remaining/undecided hunks in an editor.) Have fun! :) ...Johan -- Johan Herland, <johan@herland.net> www.herland.net -- 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
| Eric Paris | [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning |
| Mark Fasheh | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Linus Torvalds | Linux 2.6.21-rc4 |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
