From: Jon Turney <jon.turney@dronecode.org.uk>
To: rappard@dds.nl, The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] ncurses-6.3-1.20220416, dialog-1.3-4.20220117, tack-1.09-1.20210619 (TEST)
Date: Wed, 1 Jun 2022 18:53:57 +0100 [thread overview]
Message-ID: <788b6650-f85a-95be-c4bb-19b4132357d4@dronecode.org.uk> (raw)
In-Reply-To: <CACpHt-sG7tdiUFmgR+n0NH9u0R0whwUkDh+thH=0XsK8z_S4Pg@mail.gmail.com>
On 01/06/2022 16:23, rappard@dds.nl wrote:
> Hi Jon,
>
> Saw your mail on the Cygwin mailing list:
>
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * dialog-1.3-4.20220117
>> * ncurses-6.3-1.20220416
>> * tack-1.09-1.20210619
>>
>> Note: I'm updating these orphaned packages only because they are long
>> overdue an update. If anybody wants to take over maintainership, they
>> are more than welcome. (ncurses in particular is an important package,
>> with many packages depending on it).
>
> What exactly is involved in maintainership? Is there a dedicated
> (cygwin.com) page that gives a thorough outline?
I think https://cygwin.com/packaging-contributors-guide.html#submitting
tries to answer that.
If that's insufficiently thorough for you, feel free to ask questions on
the cygwin list.
Brian Inglis has adopted ncurses [1], but there are plenty of other
packages which could do with some TLC [2]...
[1] https://cygwin.com/pipermail/cygwin-apps/2022-May/042036.html
[2] https://cygwin.com/packages/reports/unmaintained.html
prev parent reply other threads:[~2022-06-01 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 19:34 Jon Turney
[not found] ` <CACpHt-sG7tdiUFmgR+n0NH9u0R0whwUkDh+thH=0XsK8z_S4Pg@mail.gmail.com>
2022-06-01 17:53 ` Jon Turney [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=788b6650-f85a-95be-c4bb-19b4132357d4@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=rappard@dds.nl \
/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).