Re: FEATURE REQUEST: git-format-path: Add option to encode patch content

Carl Worth [off-list ref] writes:

quoted

In the community git originates from, even --inline attachments
are frowned upon, let alone --attach multiparts (yes, I am
talking about the kernel list and this list).  Nobody who sends
patches over e-mail in communities that have a tradition against
unreadable patches would be using --inline nor --attach anyway,
so making --attach to do base64 would not hurt there.

I know I'm not within the kernel or git party line by saying this, but
I don't have a problem with (non base64) mime-attached patches. My MUA
displays them fine and quotes them when I reply so I can easily review
them.

You strayed into tangent here.  You said you do not have a
problem with non base64 attachments.  I would like to know if
you have or do not have problem with base64 ones, as that is
what indicates your opinion on making --attach unconditionally
do base64 which was the suggestion made in the thread.