Steffen Prohaska <prohaska@zib.de> writes:Selectively committing diff hunks also means that a subsequent rebase -i or git-cherry will have to reconsider the same commit as it has only been incompletely applied. So it can mean more work later. Also one would in general have to edit the commit message (if it describes everything that has been done). There are simply consequences for the workflow if you do things right. Whether they are worth a "big fat red warning" is one question, but mentioning them is probably not amiss. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - 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
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| David Miller | Slow DOWN, please!!! |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
git: | |
