What's new in Magit 2.x

Even if you don't use Emacs, I believe you _have_ to try magit. It will quickly become an essential part of your git workflow. You could zoom out to grasp the overall state of your project, dive into specific details and perform intricate surgery of your git history, all with single-key presses. It is pure genius.

I love magit. One gripe with the upgrade is 2.x requires a recent version of git. I use magit at work and we have to all use the same git version. It&#x27;s not a recent version so I can&#x27;t use the latest magit.<p>This is unfortunate. I wonder if the maintainers could simply disable some of the newer features if the git version is say 1.8 which would allow git luddites to benefit from the other enhancements.

I know this will be considered un-gracious and get me the &quot;learn emacs NOOB&quot; award (an editor I have been using for 20 years, just not a huge fan of the package environment).<p>But, I notice emacs packages don&#x27;t give the specific steps to follow. For instance <a href="http:&#x2F;&#x2F;magit.vc&#x2F;manual&#x2F;magit&#x2F;Updating-from-an-older-release.html" rel="nofollow">http:&#x2F;&#x2F;magit.vc&#x2F;manual&#x2F;magit&#x2F;Updating-from-an-older-release....</a> says &quot;So please uninstall the packages magit, git-commit-mode, and git-rebase-mode.&quot; No mention of what specific command will do that, what environment variable may tell you the directory location or so on. I know writing documentation is unpleasant, but it is really frustrating when you don&#x27;t connect that last inch with the exact commands.<p>Even the linked article instructions are a problem. For me the command &quot;M-x magit-version&quot; is not defined until after I run &quot;M-x magit-status&quot;. Even then the version reported is &quot;Magit 21050722.2133&quot;. Care to hazard a guess if this is a 2.X version of Magit? Is it 2.133?

Besides Emacs itself, Magit is the greatest tool in my arsenal for making clean patches and making me a more productive programmer in general. It&#x27;s made doing more advanced git tasks so much easier, interactive rebasing and staging&#x2F;unstaging hunks in particular. Can&#x27;t live without it.

Very very minor nitpick, magit-status theme (gray, brown, black) is not very welcoming. I don&#x27;t use themes so I guess these are defaults magit values. You need to put some rainbow in there :)

There&#x27;s some less great new stuff in 2.x, too, sadly: <a href="https:&#x2F;&#x2F;github.com&#x2F;magit&#x2F;magit&#x2F;issues&#x2F;2076" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;magit&#x2F;magit&#x2F;issues&#x2F;2076</a>

Kind of OT, but has anybody read this book? How good is it? Seems very interesting and the articles on the site are good too, but since it’s not on Amazon I haven’t seen any reviews.

moving from magit 1.x to this magit made me accidentally push some commits to the master branch. This is because my fingers still want to exercise the magit 1.X key combo&#x27;s. I&#x27;m sure I&#x27;m not the only one. So what&#x27;s the canonical way to: create branch X, switch to branch X, and make it so my next push will go to origin&#x2F;X ?