On Wed, Feb 1, 2023 at 12:02 PM Sean Christopherson <seanjc@xxxxxxxxxx> wrote: > > On Wed, Dec 21, 2022, Ben Gardon wrote: > > This series builds on 9352e7470a1b4edd2fa9d235420ecc7bc3971bdc. > > Before you send the next version, can you tweak your workflow to generate the > base commit via `git format-patch --base`? That makes it much easier for humans > and scripts to find the base commit, and saves you from having to remember to > manually specify the base. Because of the code movement, applying this series > without the precise base is an exercise in frustration. > > E.g. my workflow does > > git format-patch --base=HEAD~$nr <more crud> > > where $nr is the number of patches to generate. There's also an "auto" option, > but IIRC that only works if you have the upstream pointing at the base, e.g. it > falls apart if upstream points at your own remote "backup" repo. Sure thing, thanks for the tip!
