From: "Thomas Adam" <thomas.adam22@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: "Mike Dalessio" <mike@csa.net>, git@vger.kernel.org
Subject: Re: [PATCH] instaweb: support for Ruby's WEBrick server
Date: Mon, 17 Sep 2007 13:02:24 +0100 [thread overview]
Message-ID: <18071eea0709170502s397331c5j7d77aa9531f73704@mail.gmail.com> (raw)
In-Reply-To: <20070917115518.GA26815@soma>
On 17/09/2007, Eric Wong <normalperson@yhbt.net> wrote:
> Could we make the shebang dynamic? (capturing the output of `which ruby`
> maybe, or just breaking down and using /usr/bin/env ruby). The ruby
> binary seems to appear all over the place on the filesystem from my
> experience, especially with its popularity amongst OSX users.
This is what /usr/bin/env is useful for, but it's not that portable.
-- Thomas Adam
next prev parent reply other threads:[~2007-09-17 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <618c07250709161935g333f0536q31b453bd58f2d75d@mail.gmail.com>
2007-09-17 11:55 ` [PATCH] instaweb: support for Ruby's WEBrick server Eric Wong
2007-09-17 12:02 ` Thomas Adam [this message]
2007-09-17 12:25 ` Florian Weimer
2007-09-17 13:55 ` Mike Dalessio
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=18071eea0709170502s397331c5j7d77aa9531f73704@mail.gmail.com \
--to=thomas.adam22@gmail.com \
--cc=git@vger.kernel.org \
--cc=mike@csa.net \
--cc=normalperson@yhbt.net \
/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).