Quotes of the week
Posted Dec 24, 2010 16:26 UTC (Fri)
by kleptog (subscriber, #1183)
[Link] (4 responses)
The only problem I have is that since commits are simply links between two "points" I imagine it should be easy to shuffle commits around, to merge and split them. But that just doesn't seem to be that simple (or I haven't found the right tool).
Anyway, "git rebase" is cool. Just had to say that. :)
Posted Dec 24, 2010 19:03 UTC (Fri)
by jthill (subscriber, #56558)
[Link]
How would a duplicate hash in different projects cause trouble?
For history editing look at cherry-pick and reset --merge and rebase -i. If you use reset --merge to build clean presentation-quality branches without uninteresting safeties and mistakes, and then delete the noisy branches once all is good, not only is your repository a manifold but full quantum reality, virtual particles, foam and all! (I'm neither mathematician nor physicist so ttmv)
Posted Dec 24, 2010 20:23 UTC (Fri)
by rvfh (guest, #31018)
[Link] (2 responses)
I personally use
Posted Jan 1, 2011 14:25 UTC (Sat)
by kleptog (subscriber, #1183)
[Link] (1 responses)
Posted Jan 3, 2011 9:31 UTC (Mon)
by johill (subscriber, #25196)
[Link]
Quotes of the week
Quotes of the week
Quotes of the week
git rebase -i <hash>
. Isn't it what you're after?Quotes of the week
Quotes of the week