|
From: | Simon Thum |
Subject: | Re: [O] [DEV] New git workflow |
Date: | Sat, 24 Mar 2012 21:08:13 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120304 Thunderbird/10.0.1 |
Hi Daniel, On 03/24/2012 12:05 PM, Daniel Dehennin wrote:
Simon Thum<address@hidden> writes: It seems that one problem with cherry-picking is the tracking of what is in which branch and from where it comes. I'm not a git neither DVCS guru, but daggyfixes[1][2][3] is saner than cherry-picking.
I'm a bit biased as I mainly have git experience but to me it seems that both cherry-picking and daggy fixes have their strengths and weaknesses, and I'd rather have them both in all the VCSes but needless fights over which one is ultimately superior. Git should probably learn that thing, IMO.
Cheers, Simon
My 2ยข. Regards. Footnotes: [1] http://mercurial.selenic.com/wiki/DaggyFixes [2] http://wiki.monotone.ca/DaggyFixes/ [3] http://stackoverflow.com/questions/2922652/git-is-there-a-way-to-figure-out-where-a-commit-was-cherry-picked-from
[Prev in Thread] | Current Thread | [Next in Thread] |