Am Montag, den 08.02.2021, 12:15 -0500 schrieb Dmitry Polyakov:
> Leo Prikler writes:
> 
> > the patch now applies with "git apply", but not "git am", which 
> > makes
> > it difficult to sign off.  I can however rewrite the commit on your
> > behalf if that is what you want.
> 
> No, my goal is to send as good patch as possible without any stuff 
> like
> rewriting patch by maintainer. My first patch was submitting with
> copy-pasting patch from output of magit `W c c` to message-buffer,
> but
> format=flowed (as this artcle https://useplaintext.email/ urges) in 
> m4ue
> wrap some lines and therefore inline patch is brocken.
That looks like a decent recommendation for normal email, but is
inadequate for patches.  You might want to disable line wrapping for
patches.

> Second sended by `git send-email --to="46378@debbugs.gnu.org" HEAD^`.
> 
> May be I should turn off format=flowed option? Or send patch as 
> attached
> file? I dunno what way is produce minimal effort by your side, so 
> please
> tell me.
The output of git send-email *should* be compatible with git am. 
However, the mail that you've sent seems to have some of the fields
mixed up.  I'm not sure if send-email has a format=flowed option, but
if it does, you might want to uncheck it.

Don't forget to add --cc=leo.prikler@student.tugraz.at (or more
generally --cc=<reviewer>) to your invocation of `git send-email`, so
that reviewers, that are not subscribed to the ML (like myself) are
also immediately informed.

I'm personally fine with patches as attachment, but others might not
be.  I'll send one of my own commits as formatted by format-patch as an
attachment to this, so that you can cross-check your own git send-email 
setup.  Especially make sure that the header sequence matches up.

> Sorry, I literally have no expirience with email driven changes
> submitting before.
Don't worry too much about it, everyone's a beginner :)

Regards,
Leo