From: Junio C Hamano <gitster@pobox•com>
To: Ramkumar Ramachandra <artagnon@gmail•com>
Cc: Jonathan Nieder <jrnieder@gmail•com>,
Ruben Kerkhof <ruben@rubenkerkhof•com>,
Igor Gnatenko <i.gnatenko.brain@gmail•com>,
Git List <git@vger•kernel.org>
Subject: Re: [PATCH] send-email: If the ca path is not specified, use the defaults
Date: Mon, 27 Jan 2014 08:02:31 -0800 [thread overview]
Message-ID: <xmqqlhy1pg4o.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CALkWK0ky2KCJuo==XRiNu+eb2+hHpgv+FAyZTd85=TYQxgSCbQ@mail.gmail.com> (Ramkumar Ramachandra's message of "Sun, 26 Jan 2014 12:17:14 -0500")
Ramkumar Ramachandra <artagnon@gmail•com> writes:
> Junio C Hamano wrote:
>> This change could introduce a regression for people on a platform
>> whose certificate directory is /etc/ssl/certs but its IO::Socket:SSL
>> somehow fails to use it as SSL_ca_path without being told.
>
> I can confirm that my git-send-email doesn't regress to the
> pre-35035bbf state; my certificate directory is /etc/ssl/certs. I'm
> somewhat surprised that IO::Socket::SSL picks the right file/
> directory on every platform without being told explicitly. This change
> definitely looks like the right fix.
Thanks.
prev parent reply other threads:[~2014-01-27 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 17:31 [PATCH] send-email: If the ca path is not specified, use the defaults Igor Gnatenko
2014-01-15 19:26 ` Junio C Hamano
[not found] ` <7AD1C6ED-6177-415D-B342-D1FEA9F810B4@rubenkerkhof.com>
2014-01-15 21:30 ` Junio C Hamano
2014-01-15 21:50 ` Ruben Kerkhof
2014-01-15 21:50 ` Jonathan Nieder
2014-01-16 23:19 ` Junio C Hamano
2014-01-17 4:21 ` Kyle J. McKay
2014-01-17 18:14 ` Junio C Hamano
2014-01-17 23:34 ` Kyle J. McKay
2014-01-26 17:17 ` Ramkumar Ramachandra
2014-01-27 16:02 ` Junio C Hamano [this message]
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=xmqqlhy1pg4o.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=artagnon@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=i.gnatenko.brain@gmail$(echo .)com \
--cc=jrnieder@gmail$(echo .)com \
--cc=ruben@rubenkerkhof$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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