From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 8e1cfb: .travis.sh: increase the number of jobs to run in ...
Date: Sat, 17 Jun 2017 20:53:00 -0000 [thread overview]
Message-ID: <59436a242199b_145f3fbaabbfdc40562c2@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 8e1cfbdad10c50977a5a732b666333be391f9c3d
https://github.com/crosstool-ng/crosstool-ng/commit/8e1cfbdad10c50977a5a732b666333be391f9c3d
Author: Chris Packham <judge.packham@gmail.com>
Date: 2017-06-16 (Fri, 16 Jun 2017)
Changed paths:
M .travis.sh
Log Message:
-----------
.travis.sh: increase the number of jobs to run in parallel
The travis-ci.org vms have 2 cores so lets oversubscribe them a little
to speed things up.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Commit: 4c26ef68773832b3c3eb44b0eca45db95f479644
https://github.com/crosstool-ng/crosstool-ng/commit/4c26ef68773832b3c3eb44b0eca45db95f479644
Author: Chris Packham <judge.packham@gmail.com>
Date: 2017-06-16 (Fri, 16 Jun 2017)
Changed paths:
M .travis.yml
Log Message:
-----------
.travis.yml: include support for C++
This is required for building the latest gdb.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Commit: 8758457c25415a1d2f92b55f445a766a36e167d7
https://github.com/crosstool-ng/crosstool-ng/commit/8758457c25415a1d2f92b55f445a766a36e167d7
Author: Alexey Neyman <stilor@att.net>
Date: 2017-06-15 (Thu, 15 Jun 2017)
Changed paths:
M .travis.sh
M .travis.yml
Log Message:
-----------
Merge pull request #757 from cpackham/travis-updates
Travis updates
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/07a3b822f5af...8758457c2541
reply other threads:[~2017-06-16 5:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=59436a242199b_145f3fbaabbfdc40562c2@hookshot-fe3-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@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).