@Willem A separate nautilus PR is not needed.
You have to cherry-pick the master commits. Whatever relevant "extra" changes are needed for nautilus, you can make at the same time you are resolving the cherry-pick conflicts. Then, describe these changes in the "Conflicts" section along with other modifications you made.
This is not sufficiently covered by SubmittingPatches-backports.rst, unfortunately. I'm working on a new draft, which includes the following:
"Manual changes might be necessary even when a commit cherry-picks cleanly. In this case, a "Conflicts" section should be created manually. Also, when resolving conflicts for a cherry-pick, you might know that additional changes are necessary in stable branch to make the commit work there. In that case, make the changes while resolving the cherry-pick conflicts, and describe these additional changes in the "Conflicts" section.
"Rationale: Though there is a slight semantic difference between conflicts reported by git and "conflicts" that arise due to manual editing after a clean cherry-pick, the Conflicts section is where any and all manual revisions are declared, regardless of what precipitated the need for modification."
Does that make sense?