Hi Doug,
On 2/20/21 1:13 AM, Doug Evans via wrote:
When updating submodules, the commit description is a good
good place to include the output of:
$ git shortlog 8f43a99..26ae658
See for example QEMU commit f350d78f102 ("Update SLOF").
Anyhow up to the maintainer merging your patch.
Thanks, that helps a little.
The issue here is that qemu is using branch 4.2 of libslirp, whereas the patch is currently just on libslirp's master branch.
Part of the problem is the commit description, which you've helped with.
But what about the functional part of the patch?
I can only get git format-patch to include a commit id, and the only commit id available is on the libslirp master branch.
Is there an additional step I need to do like submit libslirp changes in three parts?
Step 1: Submit patch to libslirp's repo (not qemu's copy, but the libslirp master repo)
Step 2: Submit a patch to libslirp's repo to add the patch to its 4.2 branch
Step 2b: Wait for qemu's copy of libslirp's 4.2 branch to appear in qemu's libslirp repo
Step 3: Submit patch to advance qemu's libslirp submodule
I've done steps 1,3, it's just effecting the equivalent of step2 that I'm fuzzy on.