5 ms·
I would eliminate these tasks from the aspect of the user and provide a more straight forward way to accomplish the same intent. You make a good point though be
by loudthing 5y ago
I would eliminate these tasks from the aspect of the user and provide a more straight forward way to accomplish the same intent. You make a good point though because this is easier said than done with a typical terminal based application.
- jamesmontalvo3 5y agoYou want to remove fast-forward and rebase from a graph based version control system? What would you do instead? Always merge?
- apocolyps6 5y agoIt's been working for me so far :)
- aeneasmackenzie 5y agoIt sounds like he wants a GUI so you’d just drag and drop.
- emodendroket 5y agoIsn't that the hg concept, no history rewrites? Well it's more nuanced than that but you have much less freedom, I think
- rezonant 5y agoI don't think it makes sense to eliminate these, but I'll toss in "Take Commit" as an alternative name that might be more obvious than "Cherry Pick". Still, once you know it, you know it. You'd still need to understand what Take Commit means to use it effectively, but it would make it easier for a dev to learn it the first time.
- _ea1k 5y agoTake commit sounds like some weird version of merging a pull request to me. Like you've sent me some commits and now I'm going to take them. Cherry pick on the other hand has a non-technical definition that closely approximates what it does in git: https://www.merriam-webster.com/dictionary/cherry-pick https://www.merriam-webster.com/dictionary/cherry-pick