A basic SVN flow to backport a commit could look like this:
$ svn switch '^/branches/4.7'
$ svn merge -c 12345 '^/trunk'
$ svn ci
For merges you should generally use a pristine
branches/4.7 checkout that has no code changes other than what’s being merged and a test site for testing the merged commit on (which you should always do).
Also, although you’ll probably never need it, if you’re merging multiple commits one after each other, don’t forget to run svn up between them. If what you need to merge has multiple commits, also feel free to squash them down for the branch commit to make it easier for everyone reading.
Note: Make sure to run the above commands from the branch root, and not from a sub directory. The reason for this is that the
svn:mergeinfo is a SVN property on
/branches/4.7 which the SVN client sets, it’s not a server side thing.
At the bottom of https://core.trac.wordpress.org/browser/branches/4.7 you see two links, ‘merged’ and ‘eligible’. The second one shouldn’t list commits which are already merged.