From: Kees Cook <kees@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: workflows@vger.kernel.org
Subject: Re: Fcc with "git send-email"
Date: Mon, 2 Jun 2025 16:07:22 -0700 [thread overview]
Message-ID: <202506021606.A2CFEECE2@keescook> (raw)
In-Reply-To: <20250603003627.4beb1ae5@foz.lan>
On Tue, Jun 03, 2025 at 12:38:32AM +0200, Mauro Carvalho Chehab wrote:
> the tunnel script redirects the e-mails to dovecot imap daemon:
>
> #!/bin/sh
>
> export MBOX_LOCKS=fcntl
> MAIL={my_imap_folder_location}
> exec /usr/libexec/dovecot/imap
>
> With that, the e-mails go to my Drafts folder. This way, I end sending
> the e-mails prepared by git using my MUA. One of the advantages is that
> I can modify the e-mail as needed. I the case of PRs, I use it to add
> a summary of what is there at the PR.
Interesting... this is close, yeah. I end up spawning mutt directly for
my PRs, so I get the FCC. I think there must be a way to get mutt to
send an email noninteractively...
--
Kees Cook
next prev parent reply other threads:[~2025-06-02 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 19:32 Fcc with "git send-email" Kees Cook
2025-06-02 12:01 ` Mark Brown
2025-06-02 22:38 ` Mauro Carvalho Chehab
2025-06-02 23:07 ` Kees Cook [this message]
2025-06-03 4:41 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202506021606.A2CFEECE2@keescook \
--to=kees@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).