I know, this is an old question, but perhaps this helps someone in a similar situation:

In my case, I wanted to revert an "older" commit, meaning it was already pushed to the repo and already had other commits following it, but still keep its changes to build upon them. The git revert -n <sha> suggested by @WimFeijen didn't really do that.

I basically ended up doing:

git revert <sha>
git cherry-pick --no-commit <sha>
git restore -- .

What does this do? This reverts the commit normally. The cherry-pick of the same commit adds and stages all the changes again without a commit. The following restore unstages all changes so I can stage everything I need myself.

Not as straight-forward as I hoped, but did the trick for me.