Hi Philipp, On Wed, Nov 06, 2024 at 08:47:04PM GMT, Philipp Takacs wrote: > > > Actualy I tried to avoid this, because I'm not a big fan of the > > > git-send-email workflow. > > > > Is the issue with sending patches as email, or specific to > > git-send-email(1)? > > It's git-send-email(1) specific. This has two reasons: > > 1. I don't think my vcs should include a mail user agent You don't need it. In fact, I use neomutt(1) as a driver for git-send-email(1), which leaves the MUA job to neomutt(1). git-send-email(1) itself doesn't do much work. Here's what I use: $ sed -n '/^\[sendemail]/,/^[^\s]/p' ~/.gitconfig [sendemail] sendmailcmd = neomutt -C -H - && true In fact, I prefer if a real MUA does the send, because then it allows signing the emails with PGP. > 2. I would prefere to just add commits as mime attachments I accept them as mime attachments. But I strongly prefer having one patch per email. If it's okay for you to send one email per patch, and want to do it manually, I don't care too much if it's a mime attachment or inline. git-send-email(1) is nice in that regard, because it automates invoking the MUA and piping one patch to each invocation. You can (and probably have already done) check the files under ./CONTRIBUTING.d/, which detail this. > Philipp Have a lovely night! Alex -- <https://www.alejandro-colomar.es/>
Attachment:
signature.asc
Description: PGP signature
