Remove deprecated backout command from documentation table

[alper]

I just ran into this trying to figure out the equivalent to git revert. Turns out that backout is deprecated and revert does not have the same defaults.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[thoughtpolice]

Note that backout was only deprecated three weeks ago. We're probably going to leave it around for at least 3-5 releases before it at this rate, so this PR will be in limbo until then (but you can also close it & refile, leave it, whatever...)

[emilazy]

It only replaces it in the docs. (Though I think people probably want -B @ more than -d @.)

[thoughtpolice]

Ah, that's what I get for drawing conclusions from only reading the PR title. :)

[alper]

Thanks! Sorry for the confusion but I live by this table right now and it being up to date is going to help me at least.

@emilazy Didn't know what the best default would be but I changed it to your suggestion.

[PhilipMetzger]

It only replaces it in the docs. (Though I think people probably want -B @ more than -d @.)

Isn't -B @equivalent to -d @- though? Also prefix the commit message with docs: per our commit style here, https://github.com/jj-vcs/jj/blob/main/docs/contributing.md#commit-guidelines, also squash down your two commits back to one.

[emilazy]

-B @ rebases @ on top of the revert.

[alper]

Fixed up the description and squashed the commits.