From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] README: Add note about testing with Travis CI
Date: Wed, 5 Jun 2019 17:59:58 +0200 [thread overview]
Message-ID: <20190605155958.GA22233@dell5510> (raw)
In-Reply-To: <20190605153529.GA29218@rei.lan>
Hi Cyril,
> Maybe we should explain why this is a good idea, something as:
> It's a good idea to test patches on Travis CI before posting to mailing
> list. Our travis setup covers various architectures and distributions in
> order to make sure LTP compiles cleanly on most common configurations.
Thanks, good idea. Acking this?
+
+It's a good idea to test patches on Travis CI before posting to mailing
+list. Our travis setup covers various architectures and distributions in
+order to make sure LTP compiles cleanly on most common configurations.
+For testing you need to sign up to Travis CI, enable running builds on your LTP fork on
+https://travis-ci.org/account/repositories and push your branch.
Kind regards,
Petr
next prev parent reply other threads:[~2019-06-05 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 13:56 [LTP] [PATCH] README: Add note about testing with Travis CI Petr Vorel
2019-06-05 15:35 ` Cyril Hrubis
2019-06-05 15:59 ` Petr Vorel [this message]
2019-06-06 8:32 ` Cyril Hrubis
2019-06-06 8:47 ` Petr Vorel
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=20190605155958.GA22233@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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