public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto@cante.net>
To: Russell VT <russellvt@gmail.com>
Cc: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: Cygwin now on Python 3? What about Mercurial?
Date: Thu, 11 Mar 2021 13:57:10 +0200	[thread overview]
Message-ID: <YEoFlomTSAP2emis@congo.cante.net> (raw)
In-Reply-To: <CANV2+nXVtgkYSALuNzMqcN_jGtwh55JLDdKM0LiV+1pkJ4EuNA@mail.gmail.com>

On 2021-03-07 01:32, Russell VT wrote:
> On Thu, Mar 4, 2021 at 8:39 AM Ken Brown via Cygwin <cygwin@cygwin.com>
> wrote:
> 
> > On 3/4/2021 6:05 AM, marco atzeri via Cygwin wrote:
> > > On Thu, Mar 4, 2021 at 10:27 AM Russell VT via Cygwin  wrote:
> > >> Cygwin Enthusiasts!
> > >
> > > It seems the current package maintainer for Mercurial is not available
> > for
> > > the upgrade from 2.7 to 3.8.
> > > We need to decide how to proceed
> >
> > The Mercurial maintainer (Jari) doesn't always follow the mailing list.
> > I've
> > added him to the CC.
> >
> 
> Thanks Ken!
> 
> In the meantime, I'll  take a look at the Package Contributors' Guide, as
> was suggested by another... and maybe I can hell fill in some blocks with
> some of my own resources.

Mercurial was uploaded few days ago
Jari

  parent reply	other threads:[~2021-03-11 11:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  8:45 Russell VT
2021-03-04 11:05 ` marco atzeri
2021-03-04 15:19   ` Ken Brown
2021-03-04 18:32     ` Marco Atzeri
2021-03-06 14:45       ` Jari Aalto
2021-03-06 14:49         ` Marco Atzeri
2021-03-07  9:32     ` Russell VT
2021-03-07 11:58       ` Marco Atzeri
2021-04-02 13:27         ` Oleksandr Gavenko
2021-03-11 11:57       ` Jari Aalto [this message]
2021-03-04 13:30 ` Stephen John Smoogen

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=YEoFlomTSAP2emis@congo.cante.net \
    --to=jari.aalto@cante.net \
    --cc=cygwin@cygwin.com \
    --cc=kbrown@cornell.edu \
    --cc=russellvt@gmail.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).