From: Luis Lavena <luislavena@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Running rack tests on Windows (both 1.9.3 and 2.0.0)
Date: Mon, 12 Nov 2012 08:11:31 -0800 (PST) [thread overview]
Message-ID: <7740785e-b32b-4e1c-ab4f-8f83204b588f@googlegroups.com> (raw)
In-Reply-To: <3784133A-3446-430A-B961-F55F21A6F27E@finn.de>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Sunday, November 11, 2012 8:25:54 PM UTC-3, Konstantin Haase wrote:
>
> In related news: Work on windows support for Travis CI has started. It
> might take a bit, though.
>
>
Please email me more details or include me in early alpha to help you crash
the thing, or I will remove you from my friends list.
Really, I will do that.
:-D
--
Luis Lavena
[-- Attachment #2: Type: text/html, Size: 603 bytes --]
next prev parent reply other threads:[~2012-11-12 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 13:20 Running rack tests on Windows (both 1.9.3 and 2.0.0) Luis Lavena
2012-11-11 18:59 ` James Tucker
2012-11-11 23:25 ` Konstantin Haase
2012-11-12 16:11 ` Luis Lavena [this message]
2013-01-31 6:59 ` Tim Moore
2013-02-07 2:02 ` James Tucker
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7740785e-b32b-4e1c-ab4f-8f83204b588f@googlegroups.com \
--to=rack-devel@googlegroups.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).