From: noreply at jenkins-public.pelagic.nl (Pelagic Jenkins (Public) )
Subject: Jenkins build is back to normal : cgit-master-coverity #30 - origin/master - 5ccd965
Date: Fri, 25 Nov 2016 06:49:19 +0100 (CET) [thread overview]
Message-ID: <396443593.3.1480052959211.JavaMail.jenkins@jenkins-public.internal.Hupie.com> (raw)
In-Reply-To: <905960856.1.1480018749112.JavaMail.jenkins@jenkins-public.internal.Hupie.com>
https://hupie.dyndns.org:15051/jenkins/job/cgit-master-coverity/30/
prev parent reply other threads:[~2016-11-25 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 5:49 Build failed in Jenkins: cgit-master-coverity #28 - origin/master - 8e9ddd2 noreply
2016-11-24 20:19 ` Build failed in Jenkins: cgit-master-coverity #29 " noreply
2016-11-25 5:49 ` noreply [this message]
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=396443593.3.1480052959211.JavaMail.jenkins@jenkins-public.internal.Hupie.com \
--to=cgit@lists.zx2c4.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 NNTP newsgroup(s).