From: noreply at pelagic.nl (Pelagic Jenkins (Public) )
Subject: Jenkins build is back to normal : cgit-master #182 - origin/master - 7ba4196
Date: Tue, 3 Jul 2018 20:42:57 +0200 (CEST) [thread overview]
Message-ID: <618664013.8.1530643377061.JavaMail.jenkins@jenkins-public.internal.Hupie.com> (raw)
In-Reply-To: <1323576185.6.1530642922302.JavaMail.jenkins@jenkins-public.internal.Hupie.com>
See <https://hupie.dyndns.org:15051/jenkins/job/cgit-master/182/display/redirect?page=changes>
prev parent reply other threads:[~2018-07-03 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 18:30 Build failed in Jenkins: cgit-master #180 - origin/master - a35da29 noreply
2018-07-03 18:35 ` Build failed in Jenkins: cgit-master #181 - origin/master - 899f415 noreply
2018-07-03 18:42 ` 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=618664013.8.1530643377061.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).