From: Christopher Rigor <crigor@gmail.com>
To: kgio@librelist.org
Subject: Re: kgio_ext.so: [BUG] constant not a symbol or string
Date: Tue, 4 Feb 2014 10:38:04 +0800 [thread overview]
Message-ID: <CA+QCWdKQy9yuBZR_Lm5EE2NFP_Mxb-Wnh4LbKQL19MACC-jjFA@mail.gmail.com> (raw)
In-Reply-To: 20140116235455.GA30399@dcvr.yhbt.net
Sorry for the late reply Eric. Your first reply went to my spam folder.
We replaced the server and didn't see this issue again. The server is
set up the same way. We don't use RVM or similar.
Thanks for the patch. This will help in the future.
-Christopher
On Fri, Jan 17, 2014 at 7:54 AM, Eric Wong <normalperson@yhbt.net> wrote:
> Ping! Were you able to resolve this issue? Thanks.
next prev parent reply other threads:[~2014-02-04 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 6:23 kgio_ext.so: [BUG] constant not a symbol or string Christopher Rigor
2013-12-27 7:41 ` Eric Wong
2014-01-16 23:54 ` Eric Wong
2014-02-04 2:38 ` Christopher Rigor [this message]
2014-02-04 3:04 ` Eric Wong
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
List information: https://yhbt.net/kgio/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+QCWdKQy9yuBZR_Lm5EE2NFP_Mxb-Wnh4LbKQL19MACC-jjFA@mail.gmail.com \
--to=crigor@gmail.com \
--cc=kgio@librelist.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/kgio.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).