From: Anthony Green <green@redhat.com>
To: Jiri Vanek <jvanek@redhat.com>
Cc: Deepak Bhole <dbhole@redhat.com>,
Tiago Daitx <tiago.daitx@canonical.com>,
mauve-discuss@sourceware.org
Subject: Re: Project status
Date: Tue, 28 Feb 2017 12:31:00 -0000 [thread overview]
Message-ID: <8737eybiot.fsf@laptop.atgreen.org> (raw)
In-Reply-To: <779c9894-4055-85c9-d8d9-9c7c383269b1@redhat.com> (Jiri Vanek's message of "Tue, 28 Feb 2017 09:11:01 +0100")
> No, mauve is no longer run no maintained. It lot track with jdks on 1.6.0. Now we are looking to 9.
>
> J.
Thanks. I'm putting a TODO on my list for updating the current status
on the mauve web site.
AG
next prev parent reply other threads:[~2017-02-28 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 18:17 Tiago Daitx
2017-02-27 19:49 ` Anthony Green
2017-02-27 19:51 ` Deepak Bhole
2017-02-27 19:52 ` Deepak Bhole
2017-02-28 8:11 ` Jiri Vanek
2017-02-28 12:31 ` Anthony Green [this message]
2017-02-28 13:00 ` Mark Wielaard
2017-02-28 13:11 ` Anthony Green
2017-03-01 3:00 ` Andrew Hughes
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=8737eybiot.fsf@laptop.atgreen.org \
--to=green@redhat.com \
--cc=dbhole@redhat.com \
--cc=jvanek@redhat.com \
--cc=mauve-discuss@sourceware.org \
--cc=tiago.daitx@canonical.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 read-only IMAP folder(s) and NNTP newsgroup(s).