From: Jari Aalto <jari.aalto@cante.net>
To: Ken Brown <kbrown@cornell.edu>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Is the Mercurial package still maintained?
Date: Tue, 30 Jul 2019 07:44:00 -0000 [thread overview]
Message-ID: <20190730074425.GB10873@ahu.cante.net> (raw)
In-Reply-To: <ca637dcd-d9fb-9dcb-446c-c52af7bf8650@cornell.edu>
On 2019-07-18 18:47, Ken Brown wrote:
> On 7/18/2019 2:10 PM, Ti Strga wrote:
> > Hi.
> >
> > Upstream is at v5.0.2. The cygwin repo has been at 4.3.2 for almost two
> > years now, missing not only a lot of features but also the security fixes
> > in 4.7.2 and 4.9.
> >
> > Is a new package blocked waiting on other support to be completed? Or is
> > it simply orphaned and waiting for a new maintainer or NMU?
>
> The maintainer is Jari Aalto. I don't know if he reads the list, so I'm adding
> him to the CC.
I'll update it,
Jari
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-07-30 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 18:10 Ti Strga
2019-07-18 18:48 ` Ken Brown
2019-07-30 7:44 ` Jari Aalto [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=20190730074425.GB10873@ahu.cante.net \
--to=jari.aalto@cante.net \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).