From: Bruce Stephens <bruce.stephens@isode.com>
To: Dan McGee <dpmcgee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git send-email prompting too much
Date: Sat, 04 Apr 2009 18:12:07 +0100 [thread overview]
Message-ID: <80hc148hso.fsf@tiny.isode.net> (raw)
In-Reply-To: <449c10960904041002s22124b74k8440af216b1de9ee@mail.gmail.com> (Dan McGee's message of "Sat\, 4 Apr 2009 12\:02\:45 -0500")
Dan McGee <dpmcgee@gmail.com> writes:
> 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?
Yes. Apparently one uses \C-d now.
[...]
next prev parent reply other threads:[~2009-04-04 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 17:02 git send-email prompting too much Dan McGee
2009-04-04 17:12 ` Bruce Stephens [this message]
2009-04-05 2:13 ` Jay Soffian
2009-04-05 2:49 ` Jay Soffian
2009-04-05 9:45 ` Junio C Hamano
2009-04-05 3:23 ` [PATCH] send-email: fix nasty bug in ask() function Jay Soffian
2009-04-05 3:31 ` Jay Soffian
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=80hc148hso.fsf@tiny.isode.net \
--to=bruce.stephens@isode.com \
--cc=dpmcgee@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).