From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: workflows@vger.kernel.org
Subject: Re: Fcc with "git send-email"
Date: Tue, 3 Jun 2025 00:38:32 +0200 [thread overview]
Message-ID: <20250603003627.4beb1ae5@foz.lan> (raw)
In-Reply-To: <202505301222.55018E78@keescook>
Em Fri, 30 May 2025 12:32:04 -0700
Kees Cook <kees@kernel.org> escreveu:
> Hi,
>
> I'm just curious if anyone has found a workable solution for getting
> "Sent" folder copies of emails sent with "git send-email" (or similar
> tools that throw everything into "sendmail -i"). I'd really like my
> patches to show up in my "Sent" IMAP folder, but I only get this if I
> use my MUA directly (in my case, mutt).
>
> I'm thinking it might be possible set git's --sendmail-cmd= to a script
> that wraps "mutt -H ..." or "mutt -x ..." but I'm not having much luck.
>
> Has anyone else done this?
I don't do this for normal patches, but I do it on my upstream PR.
After preparing the PR e-mail with:
git request-pull {self.origin} git://{self.tree} {self.tag}
(you can use git format-email instead for patch series)
I use:
git imap-send
On my .git/config, I have:
[imap]
tunnel = {my_home_dir}/bin/dovecot-imap.sh
folder = Drafts
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.
Thanks,
Mauro
next prev parent reply other threads:[~2025-06-02 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 19:32 Kees Cook
2025-06-02 12:01 ` Mark Brown
2025-06-02 22:38 ` Mauro Carvalho Chehab [this message]
2025-06-02 23:07 ` Kees Cook
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=20250603003627.4beb1ae5@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=kees@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