Git development
 help / color / mirror / Atom feed
From: "Siwei Zhang" <oss@fourdim.xyz>
To: git@vger.kernel.org
Subject: [BUG] git-send-email hangs when sendemail.suppresscc is set without sendemail.confirm
Date: Wed, 15 Apr 2026 14:46:39 -0400	[thread overview]
Message-ID: <818da18e-f928-4473-8a37-28a737dbb261@app.fastmail.com> (raw)

When sendemail.suppresscc is configured (e.g., suppresscc=bodycc) but
sendemail.confirm is not explicitly set, git-send-email hangs
indefinitely after processing the patch headers.

Steps to reproduce:
 
    git config sendemail.suppresscc bodycc
    # Ensure sendemail.confirm is NOT set
    git config --unset sendemail.confirm
    git send-email --to="someone@example.com" HEAD^
 
Expected: email is sent (or a confirmation prompt appears)
Actual: process hangs indefinitely after printing "Adding cc:" lines
 
Workaround: explicitly set sendemail.confirm:
 
    git config sendemail.confirm always
 
Tested with git 2.53.0

Best,
Siwei

             reply	other threads:[~2026-04-15 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 18:46 Siwei Zhang [this message]
2026-04-15 19:10 ` [BUG] git-send-email hangs when sendemail.suppresscc is set without sendemail.confirm Siwei Zhang

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=818da18e-f928-4473-8a37-28a737dbb261@app.fastmail.com \
    --to=oss@fourdim.xyz \
    --cc=git@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