git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git send-email prompting too much

From
Dan McGee <dpmcgee@gmail.com>
Date
Apr 4, 2009, 17:02 UTC
Message-ID
<449c10960904041002s22124b74k8440af216b1de9ee@mail.gmail.com>

I'm guessing this is related to commit 6e1825186bd052fc1f77b7c8c9a31fbb9a67d90c but I haven't bisected yet. Having to hit enter 10 times ad the Message-ID prompt seemed a bit odd to me. Has anyone else seen this behavior?

dmcgee@galway ~/projects/git (working) $ git send-email 000* 0001-git-repack-use-non-dashed-update-server-info.patch 0002-pack-objects-report-actual-number-of-threads-to-be.patch Who should the emails appear to be from? [Dan McGee <dpmcgee@gmail.com>] Emails will be sent from: Dan McGee <dpmcgee@gmail.com> Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? Message-ID to be used as In-Reply-To for the first email? (mbox) Adding cc: Dan McGee <dpmcgee@gmail.com> from line 'From: Dan McGee <dpmcgee@gmail.com>' (body) Adding cc: Dan McGee <dpmcgee@gmail.com> from line 'Signed-off-by: Dan McGee <dpmcgee@gmail.com>'

From: Dan McGee <dpmcgee@gmail.com>
To: git@vger.kernel.org
Cc: Dan McGee <dpmcgee@gmail.com>
Subject: [PATCH 1/2] git-repack: use non-dashed update-server-info
Date: Sat,  4 Apr 2009 11:59:55 -0500
Message-Id: <1238864396-8964-1-git-send-email-dpmcgee@gmail.com>
X-Mailer: git-send-email 1.6.2.2.404.ge96f3.dirty
    The Cc list above has been expanded by additional
    addresses found in the patch commit message. By default
    send-email prompts before sending whenever this occurs.
    This behavior is controlled by the sendemail.confirm
    configuration setting.
    For additional information, run 'git send-email --help'.
    To retain the current behavior, but squelch this message,
    run 'git config --global sendemail.confirm auto'.
Send this email? ([y]es|[n]o|[q]uit|[a]ll): a
OK. Log says:
Sendmail: /usr/bin/msmtp -i git@vger.kernel.org dpmcgee@gmail.com
From: Dan McGee <dpmcgee@gmail.com>
To: git@vger.kernel.org
Cc: Dan McGee <dpmcgee@gmail.com>
Subject: [PATCH 1/2] git-repack: use non-dashed update-server-info
Date: Sat,  4 Apr 2009 11:59:55 -0500
Message-Id: <1238864396-8964-1-git-send-email-dpmcgee@gmail.com>
X-Mailer: git-send-email 1.6.2.2.404.ge96f3.dirty
Result: OK
(mbox) Adding cc: Dan McGee <dpmcgee@gmail.com> from line 'From: Dan
McGee <dpmcgee@gmail.com>'
(body) Adding cc: Dan McGee <dpmcgee@gmail.com> from line
'Signed-off-by: Dan McGee <dpmcgee@gmail.com>'
OK. Log says:
Sendmail: /usr/bin/msmtp -i git@vger.kernel.org dpmcgee@gmail.com
From: Dan McGee <dpmcgee@gmail.com>
To: git@vger.kernel.org
Cc: Dan McGee <dpmcgee@gmail.com>
Subject: [PATCH 2/2] pack-objects: report actual number of threads to be used
Date: Sat,  4 Apr 2009 11:59:56 -0500
Message-Id: <1238864396-8964-2-git-send-email-dpmcgee@gmail.com>
X-Mailer: git-send-email 1.6.2.2.404.ge96f3.dirty
In-Reply-To: <1238864396-8964-1-git-send-email-dpmcgee@gmail.com>
References: <1238864396-8964-1-git-send-email-dpmcgee@gmail.com>
Result: OK
Next: Bruce Stephens
Message 1 of 7 in “git send-email prompting too much”
  1. Dan McGeeApr 4, 2009
  2. Bruce StephensApr 4, 2009
  3. Jay SoffianApr 5, 2009
  4. Jay SoffianApr 5, 2009
  5. Junio C HamanoApr 5, 2009
  6. send-email: fix nasty bug in ask() functionJay Soffian, Apr 5, 2009
  7. Jay SoffianApr 5, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.