Petr Baudis:As my workflow sometimes make me do cherry-picks where history does matter, in form of me doing a "partial merge" of one or more than one commit from branch A into branch B, which does not necessarily have to be directly related, is there a way to perform something like that, while keeping history? Perhaps I'm damaged by having used CVS for too long, and merging just some files, or abusing CVS internals to make some files on branch A also be part of branch B by having their branches point to the same RCS branch revision number, but sometimes I find that I miss being able to do it in Git. Not really a big deal, just curious. -- \\// Peter - http://www.softwolves.pp.se/ -- 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
| Justin C. Sherrill | Re: pkgsrc bulk build and tiff |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Ingo Molnar | [crash, bisected] Kernel BUG at ffffffff8079afb1 (__netif_schedule()) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Evgeniy Polyakov | Re: tbench wrt. loopback TSO |
