Git development
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFH Patch 2/2] http_init(): Fix config file parsing
Date: Mon, 9 Mar 2009 23:05:53 -0400	[thread overview]
Message-ID: <76718490903092005n66bca743t67eb7f0ff830d9d7@mail.gmail.com> (raw)
In-Reply-To: <7vfxhmce67.fsf@gitster.siamese.dyndns.org>

On Mon, Mar 9, 2009 at 10:19 PM, Junio C Hamano <gitster@pobox.com> wrote:
>  * This is what I need help from people who actually do use http transport
>   and extra set of eyeballs to spot silly mistakes.

It looks sane to me.

> @@ -241,14 +221,18 @@ void http_init(struct remote *remote)
>        if (getenv("GIT_SSL_NO_VERIFY"))
>                curl_ssl_verify = 0;
>
> -       ssl_cert = getenv("GIT_SSL_CERT");
> +       if (getenv("GIT_SSL_CERT"))
> +               ssl_cert = getenv("GIT_SSL_CERT");
>  #if LIBCURL_VERSION_NUM >= 0x070902
> -       ssl_key = getenv("GIT_SSL_KEY");
> +       if (getenv("GIT_SSL_KEY"))
> +               ssl_key = getenv("GIT_SSL_KEY");
>  #endif
>  #if LIBCURL_VERSION_NUM >= 0x070908
> -       ssl_capath = getenv("GIT_SSL_CAPATH");
> +       if (getenv("GIT_SSL_CAPATH"))
> +               ssl_capath = getenv("GIT_SSL_CAPATH");
>  #endif
> -       ssl_cainfo = getenv("GIT_SSL_CAINFO");
> +       if (getenv("GIT_SSL_CAINFO"))
> +               ssl_cainfo = getenv("GIT_SSL_CAINFO");

Would these be a little cleaner with a temporary variable. e.g.

char *value;

if ((value = getenv("GIT_SSL_CERT")))
    ssl_cert = value;


j.

  reply	other threads:[~2009-03-10  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  2:19 [RFH Patch 2/2] http_init(): Fix config file parsing Junio C Hamano
2009-03-10  3:05 ` Jay Soffian [this message]
2009-03-10 11:07   ` Johannes Schindelin

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=76718490903092005n66bca743t67eb7f0ff830d9d7@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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