From: Tay Ray Chuan <rctay89@gmail.com>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: t5541-http-push hanging
Date: Wed, 11 Nov 2009 23:47:33 +0800 [thread overview]
Message-ID: <be6fef0d0911110747k219e1fe0l7bd19bbc58b5ea3e@mail.gmail.com> (raw)
In-Reply-To: <B17AB159-E217-4E1F-BEA3-97E5892C13F4@gernhardtsoftware.com>
Hi,
On Wed, Nov 11, 2009 at 2:28 PM, Brian Gernhardt
<brian@gernhardtsoftware.com> wrote:
> error: RPC failed; result=22, HTTP code = 500
> ^CFATAL: Unexpected exit with code 130
looks like an apache/http-backend issue. What version of apache are you running?
Also, are you running out of the 'next' branch?
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2009-11-11 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:28 t5541-http-push hanging Brian Gernhardt
2009-11-11 15:47 ` Tay Ray Chuan [this message]
2009-11-11 16:53 ` Brian Gernhardt
2009-11-11 15:50 ` Shawn O. Pearce
2009-11-12 4:26 ` Shawn O. Pearce
2009-11-12 4:49 ` Shawn O. Pearce
2009-11-12 5:18 ` Brian Gernhardt
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=be6fef0d0911110747k219e1fe0l7bd19bbc58b5ea3e@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
/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).