From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Travis integration
Date: Tue, 26 Mar 2013 08:11:50 +0100 [thread overview]
Message-ID: <51514A36.5040907@gaute.vetsj.com> (raw)
In-Reply-To: <sup-heliotrope/sup/pull/9/c15243758@github.com>
Hi,
Travis integration: I think this is a good idea, especially if we get
more tests up and running. My biggest annoyance, charset-issues, could
potentially greatly benefit from this. Every time something new is
implemented or something is changed it is very easy to forget to test
for ASCII / UTF-8 / whatever conversion/mixing and so on, it would be
great with a general test that could be easily adapted for theses cases.
@Whyme: How does your Travis integration work with the new 'test' target?
What do you think about including the few files that are in the main
repositories?
- Gaute
-------- Original Message --------
Subject: Re: [sup] Convert use of Rake::GemPackageTask to
Gem::PackageTask (#9)
Date: Thu, 21 Mar 2013 08:04:54 -0700
From: Whyme.Lyu <notifications@github.com>
Reply-To: sup-heliotrope/sup
<reply+i-11837079-94d5e391deb98d79554cc13e2825e2d1dcf6c79a-56827@reply.github.com>
To: sup-heliotrope/sup <sup@noreply.github.com>
CC: Gaute Hope <eg@gaute.vetsj.com>
+1 for merging this. With this patch and #10 and #11 applied, I can do
`rake gem` locally. And I'm about to setup Travis integration. Even if
there're no tests, it'd be much better to just do a smoking build and
release a usable gem soon.
---
Reply to this email directly or view it on GitHub:
https://github.com/sup-heliotrope/sup/pull/9#issuecomment-15243758
next parent reply other threads:[~2013-03-26 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sup-heliotrope/sup/pull/9/c15243758@github.com>
2013-03-26 7:11 ` Gaute Hope [this message]
2013-03-26 11:42 ` [sup-talk] " Whyme Lyu
2013-03-26 22:53 ` Gaute Hope
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=51514A36.5040907@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=sup-talk@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox