‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, February 16, 2020 7:06 PM, Segher Boessenkool <seg...@kernel.crashing.org> wrote:
> On Sat, Feb 15, 2020 at 05:22:09PM +0000, GT wrote: > > I have not been able to configure protonmail for either git imap-send or > > send-email. > > Do you use git format-patch? You should, as the manual pages for both > git imap-send and git send-email explain. > > > Will try pasting the .patch inline as plain text and see if that works. > > That doesn't work, unless you take extreme care. It is fine for showing > small snippets, but it does not result in patches people can apply. > I have more patches I'd like to post and I have been unable to find an alternative to sending them as binary attachments. 1. The only system I have access to is a Windows 10 machine. I am not allowed to modify it in any way. So I can't install cygwin (or any other software), if having that would have solved my issues. 2. I am creating the patches on a VM in one of the clouds IBM makes available for POWER software development. To access the VM the only option I have thus far is to login using Openstack from a browser. Then open a console in the interface. To get patches out of the VM, I push them onto Github. Then download them onto the Windows PC to send as email attachments. 3. On the VM git imap-send and send-email are not usable for me at the moment. Gmail now requires 2-factor authentication for them. And that in turn requires a cell phone. I can't say when I will have a new phone. Anyone have ideas on how to avoid the binary attachements? Bert.
