From: John Keeping <john@keeping.me.uk>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2015, #04; Tue, 24)
Date: Wed, 25 Nov 2015 10:13:42 +0000 [thread overview]
Message-ID: <20151125101342.GE18913@serenity.lan> (raw)
In-Reply-To: <20151125010722.GA23632@sigill.intra.peff.net>
On Tue, Nov 24, 2015 at 08:07:23PM -0500, Jeff King wrote:
> * jk/send-email-ssl-errors (2015-11-24) 1 commit
> - send-email: enable SSL level 1 debug output
>
> Improve error reporting when SMTP TLS fails.
>
> Will merge to 'next'.
Can you hold off on this one? I think my last-minute change not to
switch on --smtp-debug has introduced a Perl warning that needs to be
suppressed.
next prev parent reply other threads:[~2015-11-25 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 1:07 What's cooking in git.git (Nov 2015, #04; Tue, 24) Jeff King
2015-11-25 10:13 ` John Keeping [this message]
2015-11-25 10:15 ` Jeff King
2015-11-28 15:40 ` brian m. carlson
2015-11-28 16:35 ` Jeff King
2015-11-28 17:09 ` brian m. carlson
2015-12-01 23:10 ` Jeff King
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=20151125101342.GE18913@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).