unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [PATCH] show configuration file path in errors instead of '(eval)'
Date: Tue, 13 Oct 2009 23:17:47 -0700	[thread overview]
Message-ID: <20091014061747.GA15010@dcvr.yhbt.net> (raw)
In-Reply-To: <1255487661-20498-1-git-send-email-sunaku@gmail.com>

"Suraj N. Kurapati" <sunaku@gmail.com> wrote:
> also __FILE__ did not reflect configuration file path
> ---
>  lib/unicorn/configurator.rb |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Thanks Suraj!  Applied and pushed out.

-- 
Eric Wong

      parent reply	other threads:[~2009-10-14  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  2:34 [PATCH] show configuration file path in errors instead of '(eval)' Suraj N. Kurapati
2009-10-14  2:38 ` Suraj Kurapati
2009-10-14  6:17 ` Eric Wong [this message]

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/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091014061747.GA15010@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.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/unicorn.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).