From: "Tom G. Christensen" <tgc@jupiterrise.com>
To: Jeff King <peff@peff.net>
Cc: Patrick Steinhardt <ps@pks.im>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: git segfaults on older Solaris releases
Date: Sat, 9 Apr 2016 22:17:56 +0200 [thread overview]
Message-ID: <57096374.6030608@jupiterrise.com> (raw)
In-Reply-To: <20160409173904.GA5127@sigill.intra.peff.net>
On 09/04/16 19:39, Jeff King wrote:
> [1/3]: config: lower-case first word of error strings
> [2/3]: git_config_set_multivar_in_file: all non-zero returns are errors
> [3/3]: git_config_set_multivar_in_file: handle "unset" errors
>
I applied them to 2.8.1 and ran the testsuite again on Solaris 8/x86 and
the segfault is gone.
-tgc
next prev parent reply other threads:[~2016-04-09 20:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 18:18 git segfaults on older Solaris releases Tom G. Christensen
2016-04-07 18:32 ` Junio C Hamano
2016-04-07 18:50 ` Junio C Hamano
2016-04-07 18:56 ` David Turner
2016-04-07 19:07 ` Jeff King
2016-04-07 19:37 ` Junio C Hamano
2016-04-07 20:24 ` Jeff King
2016-04-07 20:19 ` Tom G. Christensen
2016-04-09 7:02 ` Tom G. Christensen
2016-04-09 17:39 ` Jeff King
2016-04-09 17:42 ` [PATCH 1/3] config: lower-case first word of error strings Jeff King
2016-04-09 17:42 ` [PATCH 2/3] git_config_set_multivar_in_file: all non-zero returns are errors Jeff King
2016-04-09 17:43 ` [PATCH 3/3] git_config_set_multivar_in_file: handle "unset" errors Jeff King
2016-04-09 20:17 ` Tom G. Christensen [this message]
2016-04-09 20:35 ` git segfaults on older Solaris releases Jeff King
2016-04-12 10:21 ` Patrick Steinhardt
2016-04-07 18:58 ` Tom G. Christensen
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=57096374.6030608@jupiterrise.com \
--to=tgc@jupiterrise.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.