git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kellogg-Stedman <lars@redhat.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3] http: add support for specifying an SSL cipher list
Date: Thu, 7 May 2015 14:48:04 -0400	[thread overview]
Message-ID: <20150507184804.GF16334@redhat.com> (raw)
In-Reply-To: <CAPig+cSPGguo1mEqfCTpLbHuCMaKkH8YQhoDCOPM82Fjt0C+eg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 904 bytes --]

On Thu, May 07, 2015 at 02:41:07PM -0400, Eric Sunshine wrote:
> Format multi-line comments like this:
> 
>     /*
>      * This is a multi-line
>      * comment.
>      */

Noted, thanks.

> > +       if (ssl_cipherlist != NULL && ssl_cipherlist[0] != '\0')
> 
> In git code, this is usually spelled:
> 
>     if (ssl_cipherlist && *ssl_cipherlist)

Huh.  At least in http.c, explicit checks against NULL seem more
common:

    if (ssl_cert != NULL)
    if (ssl_key != NULL)
    if (ssl_capath != NULL)

Etc.  I was just trying to make the new code look like the existing
code.  If nobody else has an opinion on this, I'm inclined to leave
the first clause as-is so that it matches and change the check for an
empty string.

-- 
Lars Kellogg-Stedman <lars@redhat.com> | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack          | http://blog.oddbit.com/


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-05-07 18:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 14:16 [PATCH] add support for specifying an SSL cipher list Lars Kellogg-Stedman
2015-05-07 15:53 ` Junio C Hamano
2015-05-07 16:04   ` Lars Kellogg-Stedman
2015-05-07 16:33     ` Junio C Hamano
2015-05-07 16:58       ` Lars Kellogg-Stedman
2015-05-07 16:08   ` [PATCH v2] http: " Lars Kellogg-Stedman
2015-05-07 16:42 ` [PATCH] " Tay Ray Chuan
2015-05-07 16:57   ` Lars Kellogg-Stedman
2015-05-07 18:17 ` [PATCH v3] http: " Lars Kellogg-Stedman
2015-05-07 18:41   ` Eric Sunshine
2015-05-07 18:48     ` Lars Kellogg-Stedman [this message]
2015-05-07 18:54       ` Eric Sunshine
2015-05-07 20:51   ` Junio C Hamano
2015-05-08  3:44 ` [PATCH v4] " Lars Kellogg-Stedman
2015-05-08  3:53   ` Eric Sunshine
2015-05-08 12:15   ` SZEDER Gábor
2015-05-08 15:59     ` Junio C Hamano
2015-05-08 13:22 ` [PATCH v5] " Lars Kellogg-Stedman
2015-05-14 19:25   ` Lars Kellogg-Stedman
2015-05-14 19:39     ` Eric Sunshine

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=20150507184804.GF16334@redhat.com \
    --to=lars@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sunshine@sunshineco.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).