public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: Re: Is the Mercurial package still maintained?
Date: Thu, 18 Jul 2019 18:48:00 -0000	[thread overview]
Message-ID: <ca637dcd-d9fb-9dcb-446c-c52af7bf8650@cornell.edu> (raw)
In-Reply-To: <CAHfZ7Xpr2FzLz=xdsawrV-VTDKuxEqFG5ccMpiRMN=Tv4CLcXA@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 703 bytes --]

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.

Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-07-18 18:48 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 [this message]
2019-07-30  7:44   ` Jari Aalto

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=ca637dcd-d9fb-9dcb-446c-c52af7bf8650@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=jari.aalto@cante.net \
    /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).