From: "Tom G. Christensen" <tgc@jupiterrise•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org, Jeff King <peff@peff•net>
Subject: Re: git segfaults on older Solaris releases
Date: Thu, 7 Apr 2016 22:19:32 +0200 [thread overview]
Message-ID: <5706C0D4.9030707@jupiterrise.com> (raw)
In-Reply-To: <xmqqk2k9z20p.fsf@gitster.mtv.corp.google.com>
On 07/04/16 20:50, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox•com> writes:
> So perhaps this is all we need to fix your box.
>
> setup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Yes that seems to work very well.
I applied this patch to 2.8.0 and have completed a testsuite run on
Solaris 2.6/x86 with only a few unrelated problems.
I will continue testing on the other Solaris < 10 releases but I do not
expect any difference in the outcome.
-tgc
next prev parent reply other threads:[~2016-04-07 20:20 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 [this message]
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 ` git segfaults on older Solaris releases Tom G. Christensen
2016-04-09 20:35 ` 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=5706C0D4.9030707@jupiterrise.com \
--to=tgc@jupiterrise$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
/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