On 22/08/13 09:24, Josh Cepek wrote: > Patch/description attached; this resolves bug #320.
ACK to patch 24be21ea2f1d02631685a0a11bf187372cf10fa4 in the attachement. > On an unrelated note, I'm trying out OpenPGP/MIME (RFCs 4880 & 3156) in > this submission since it appears the only non-broken way to sign > patches. Sane clients should eat this fine (Outlook Express may not.) If > this poses a particular problem for you or an archiving service (sf.net, > gmane, etc) I'd like to know about it. I've had issues without PGP/MIME as well, mostly due to bad wrapping. Not sure if that was issues caused by GPG, Engimail or Thunderbird. I've used PGP/MIME here for quite some time now without any complaints. Other than that, I usually just use 'git send-email' when sending patches to the mailing list. It makes the patch submission easier, and you avoid MUAs messing up the content. -- kind regards, David Sommerseth
signature.asc
Description: OpenPGP digital signature
