On Tue, 2024-02-06 at 11:49 -0800, Sean Christopherson wrote: > On Tue, Feb 06, 2024, David Woodhouse wrote: > > That isn't Unicode. Well, it *is*, but it's the subset of Unicode which > > is also plain old legacy 8-bit ISO8859-1. For some reason, Evolution > > has converted those spaces to non-breaking spaces. I have no idea why > > it's suddenly started doing that; this is a Long Term Nosupport distro > > that $employer forces me to use, and it hasn't even been updated for > > over a year. > > Out of genuine curiosity, why not use `git send-email`? I generally do for a series, but a single patch sometimes isn't even the latest or only thing in my working tree, and it's trivial enough to just dump it into the Drafts folder then edit it from there. And it's (almost) always worked in the past; as I said, I have no idea why it suddenly regressed. I do prefer to actually *read* the patch and the commit message one last time in the mailer before pressing 'send'. I do catch things that way. > > The patch is in > > https://git.infradead.org/?p=users/dwmw2/linux.git;a=shortlog;h=refs/heads/xenfv > > where I'd gathered everything that was pending, but if you prefer I'll > > also resend it later when I deal with the locking thing we discussed a > > few minutes ago. > > I'd prefer a resend so that I generate a lore link to exactly what I applied. > No rush on either patch, I'm going to be mostly offline from now-ish through > tomorrow. Ack. I'll send something based on what I find in your kvm-x86 tree. You have the first 19 of Paul's series, just not the __kvm_gpc_refresh() one at the end, right?
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
