Earlier quoted context omitted.
> Why do people make a huge fuss over git? Why? It's unclear to me what you're referring to, but the part I can answer is this: > How is git hard? IMHO because it is not intuitively obvious what it means for your "HEAD" to be "detached", or for you to "rebase" onto a "remote branch", or why "checking out" a file reverts your changes, or why "checking out" a branch suddenly clones its files, or why you'd "add" a missi…
I want to edit the commit message of a commit that is 5 commits in the past, that I have not pushed yet. What is the command to do it? Okay so it turns out I made a minor typo in that commit and I want to change it without adding any more commits. What is the command to do it? Okay so now I want to take all commits that have "bugfix pickme" in the subject and cherry-pick them to master. What is the command to do it?…
> Okay so it turns out I made a minor typo in that commit and I want to change it without adding any more commits. What is the command to do it?
It seems pretty easy to do an interactive rebase for both these.
> Okay so now I want to take all commits that have "bugfix pickme" in the subject and cherry-pick them to master. What is the command to do it?
This would be pretty simple if you know the hashs of the commits you want to bring over, but more troublesome if you don't. But I can't think of a good interface that makes this trivial without having a specific command for just this action. If this is a common action you do it would be pretty simple make a script which would make that specific command.
Additionally, an interactive rebase can hammer this screw too. With an editor that can delete lines that don't match a regex you can simply rebase your bugfix branch on top of master and get rid of all commits that aren't bugfixes.
I would say that git's existing interface solves this as well as you could expect a GUI or CLI frontend like the post to do.