git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: sig-scan-admin@synopsys.com, git-for-windows@googlegroups.com, git <git@vger.kernel.org>
Subject: Re: Will Coverity for FOSS be in scheduled maintenance mode forever?
Date: Mon, 26 Mar 2018 23:22:42 +0000
Message-ID: <CAGZ79kZRSKnS_ChC2eYRyrk4FCjE6vxstezvBWuhYfZxX_9Fhg@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1803131457310.20700@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>

On Tue, Mar 13, 2018 at 7:00 AM Johannes Schindelin <
Johannes.Schindelin@gmx.de> wrote:

> Hi Coverity (now Synopsys) team,

> I probably managed to miss important mails such as announcing that the
> Coverity service for FOSS projects would be unavailable for some time.

> Since February 20th, this seems to be the case (all attempts at even
> looking at past results redirects to https://brb.synopsys.com/ without any
> helpful further information), at least for the Git for Windows project.

> Is the deal off? Or will Coverity for FOSS come back? If the latter, when?

I noticed that there was an off period, but right now I can access it again.

Thanks for writing this email, it reminded me to check for the setup of Git
as well, which was not executed nightly since Nov 20th last year.
(the day when I migrated to a new machine... duct tape everywhere)

Thanks,
Stefan

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 14:00 Johannes Schindelin
2018-03-26 23:22 ` Stefan Beller [this message]

Reply instructions:

You may reply publically 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGZ79kZRSKnS_ChC2eYRyrk4FCjE6vxstezvBWuhYfZxX_9Fhg@mail.gmail.com \
    --to=sbeller@google.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=sig-scan-admin@synopsys.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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox