> Well, the question was not very well stated. I know what it means --I often get big hunk just because I modified whitespaces around relevent pieces of code, the ability to segment the changes and only pick isolated and specific lines for a commit (not commiting whitespaces surrounding real code changes) would be very welcome. Maybe I should know better, but the actual hunk selection in git gui is quite good already, but the ability to be more precise on how a hunk is defined is a welcome change. - jfv - 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
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Trond Myklebust | Re: (NFS) BUG: at page-writeback.c:829 [Was: 2.6.22-rc1-mm1] |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
