On Mon, 2007-10-22 at 09:59 +0200, Andreas Ericsson wrote:Hmmm, I don't really want to turn the "summary" thread into oodles of sub-threads, but here goes :) Personally I find git-blame *EXTREMELY* useful. The workflow is: 1. Bug #12345 for FooApp gets assigned to you. 2. git-svn clone fooapp's repository 3. git checkout -b my-bugfix-branch-for-12345 4. debug debug debug 5. "WTF? Who wrote this crappy code?" 6. git blame culprit-file.c 7. "Oh, it was $person with $commit_id... what were they thinking at the time?" 8. git show $commit_id 9. "Oh, I see their intentions now... what was going on at that time?" 10. git log <date range around $commit_id> 11. etc. Git-blame is very nice for code archaeology (long explanation at http://mail.gnome.org/archives/desktop-devel-list/2007-September/msg00238.html). This would be simply fantastic. If those help topics suggested workflows, I'd be delighted :) Feel free to poke me if you write up some text; I'd love to help on this. Federico - 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
| Kok, Auke | Re: -mm merge plans for 2.6.23 - ioat/dma engine |
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Matthew Garrett | [PATCH] Remove process freezer from suspend to RAM pathway |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
git: | |
