Re: [update] sysutils/trash-d 18 -> 19

2024-08-27T14:16:22Z "Stuart Henderson" <stu@spacehopper.org>:
> On 2024/08/27 16:08, Johannes Thyssen Tishman wrote:
> > 2024-08-27T13:59:36Z "Stuart Henderson" <stu@spacehopper.org>:
> > > On 2024/08/27 09:49, A Tammy wrote:
> > > >
> > > > On 8/27/24 7:26 AM, Johannes Thyssen Tishman wrote:
> > > > > 2024-08-27T11:21:50Z "Johannes Thyssen Tishman" <johannes@thyssentishman.com>:
> > > > >> Please find below an update for sysutils/trash-d to version 19.
> > > > >>
> > > > >> I just discovered this port that I'd like to try out and saw that it was
> > > > >> outdated. Although there are virtually no changes in this update, Dub
> > > > >> now requires SemVer for packages which allows us to drop our patches.
> > > > >>
> > > > >> Additionally, the man page is now generated with ronn. I wasn't sure if
> > > > >> I should add this step in the do-install hook because I'd have to
> > > > >> hard-code the ronn33 binary and I assume the name will change when the
> > > > >> ruby version changes as well. Is something like ronn${RUBY_VERSION}
> > > > >> possible?
> > > > > Oops, forgot to drop REVISION. Please find the updated diff below.
> > > >
> > > > patch is malformed and can't be applied, can you resend with correct
> > > > formatting?
> > >
> > > It was sent with quoted-unreadable formatting, from mutt hit v
> > > then "| patch -d [...]" alternatively run it through munpack (in
> > > the mpack package).
>
> oops, sorry wrong thing - run it through "qprint -d"
>
> > Hmm, that's weird. Sorry about that and thanks for the information
> > Stuart. I'm not sure I understand what the problem is or how to fix it.
> > I'm using mail/aerc with pretty much a default configuration for
> > composing email. Stuart, would you be so kind to point me to some
> > documentation about what the 'v' keybind in mutt does to troubleshoot
> > this please?
>
> The default binding for 'v' displays the various mime body parts,
> and if you | from there, it pipes the decoded version of the current
> part.
>
> Whereas if you | from the normal message viewer it sends the raw
> (undecoded) message.
>
> See "Content-Transfer-Encoding: quoted-printable" in headers.

Thanks Stuart. Is this something acceptable or should I configure my
email client to not include this header for when sending patches in the
mailing list?