From: Sverre Rabbelier <srabbelier@gmail.com>
To: Sam Vilain <sam@vilain.net>
Cc: Will Palmer <wmpalmer@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Apology/Bug report: git-send-email sends everything on Ctrl+C
Date: Wed, 26 May 2010 11:07:02 +0200 [thread overview]
Message-ID: <AANLkTin51a4RONmN6j3GXGJQ3UtE8bt3e_PF5t75mZTC@mail.gmail.com> (raw)
In-Reply-To: <4BFCE12E.4070009@vilain.net>
Heya,
[sorry for my earlier reply to your other accidental mail, feel free
to ignore it as I had not read this thread yet]
On Wed, May 26, 2010 at 10:51, Sam Vilain <sam@vilain.net> wrote:
> Hard to know what could have possibly stopped this from happening. PEBKAC.
Perhaps git can be smart and ask for confirmation for huge (>20 ?) patchsets.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-05-26 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 6:04 Apology/Bug report: git-send-email sends everything on Ctrl+C Sam Vilain
2010-05-26 6:50 ` Sam Vilain
2010-05-26 8:05 ` Will Palmer
2010-05-26 8:51 ` Sam Vilain
2010-05-26 9:07 ` Sverre Rabbelier [this message]
2010-05-26 9:16 ` Michael J Gruber
2010-05-26 9:27 ` Sam Vilain
2010-05-26 8:40 ` Michael J Gruber
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=AANLkTin51a4RONmN6j3GXGJQ3UtE8bt3e_PF5t75mZTC@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
--cc=wmpalmer@gmail.com \
/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).