Front page | perl.perl5.porters |
Postings from March 2023
Paul "LeoNerd" Evans wrote: >That's because I copied it *totally* manually by copy-pasting out of my >(non-gmail) local email client into github, and fixed up all the >\,-style escaping in the plaintext part while I was there. Oh dear. That was not a plain text document (in the sense of text/plain), all the "\," stuff is Markdown markup. Providing the bug report as a Markdown document was meant to be a convenience for GitHub users. This is not going anything like as smoothly as intended. >It is not a sustainable process that I have any interest in continuing >for the long-term. You certainly shouldn't be needing to manually edit in the kind of way you're describing. Can you suggest a better form for bug reports in email? I'm willing to author bug reports either as plain text or as Markdown, and the email headers are negotiable. We ought to be able to come up with something that's reasonably convenient on your end. (Unless you find the whole concept of bug reports in email unacceptably inconvenient.) Btw, a couple of people have said something about my message appearing as an attachment. In the form in which it went through p5p, there is no attachment in the sense of a multipart MIME message. It was a single-part message, the top-level body being of text/markdown type. -zeframThread Previous