From: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>
To: kawa@sourceware.org
Subject: Re: please checkout Kawa from gitlab.com
Date: Fri, 25 Nov 2016 01:33:00 -0000 [thread overview]
Message-ID: <20161125013303.ljc2cop3pzwhym34@odessa> (raw)
In-Reply-To: <ec5550a9-11a8-ce9b-3104-c3736bfd28a2@bothner.com>
On Tue, Nov 22, 2016 at 08:56:35AM -0800, Per Bothner wrote:
> https://gitlab.com/kashell/Kawa
>
> To check it out do:
> git clone https://gitlab.com/kashell/Kawa.git
Hi.
I've verified that the following allows you to automagically build and
run tests on the Gitlab CI:
https://gitlab.com/kumanna/Kawa/raw/c066d65d5fc36ae09f2af8491dafb253dea658e1/.gitlab-ci.yml
You can see a sample build and test here:
https://gitlab.com/kumanna/Kawa/builds/6617815
https://gitlab.com/kumanna/Kawa/builds/6617816
You might want to consider checking it in. I'l also see if I can hack
a gitignore over the weekend, if you haven't done so already.
Thanks.
Kumar
--
Kumar Appaiah
next prev parent reply other threads:[~2016-11-25 1:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 0:59 proposal: move Kawa from Subversion to git on gitlab.com Per Bothner
2016-11-13 4:42 ` Jamison Hope
2016-11-13 5:06 ` Per Bothner
2016-11-16 0:53 ` invoke branch (was: proposal: move Kawa from Subversion to git on gitlab.com) Per Bothner
2016-11-13 17:51 ` proposal: move Kawa from Subversion to git on gitlab.com David Pirotte
2016-11-13 22:55 ` Charlie Turner
2016-11-13 23:37 ` Per Bothner
2016-11-22 16:57 ` please checkout Kawa from gitlab.com Per Bothner
2016-11-22 22:12 ` David Pirotte
2016-11-23 7:42 ` Per Bothner
2016-11-23 13:17 ` make kawa-manual.epub (Re: please checkout Kawa from gitlab.com) Sudarshan S Chawathe
2016-11-23 18:05 ` Per Bothner
2016-11-27 6:07 ` Per Bothner
2016-11-25 1:33 ` Kumar Appaiah [this message]
2016-11-25 5:33 ` please checkout Kawa from gitlab.com Per Bothner
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=20161125013303.ljc2cop3pzwhym34@odessa \
--to=a.kumar@alumni.iitm.ac.in \
--cc=kawa@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).