From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITCoM] coreutils
Date: Wed, 4 May 2022 09:49:42 +0200 [thread overview]
Message-ID: <YnIwFm+EEqBZWD8r@calimero.vinschen.de> (raw)
In-Reply-To: <88171af4-4425-1923-2641-94dfbbd769e5@SystematicSw.ab.ca>
On May 2 23:15, Brian Inglis wrote:
> Hi folks,
>
> Eric Blake no longer seems to have free time available for Cygwin package
> upgrades, so I would like to offer to co-maintain coreutils and provide
> upgrades as they are now five years old.
>
> I would like to provide an upgrade to the final version 8 release 8.32,
> initially as a TEST release, before working on the latest release 9.1.
>
> Package sources and archives are available online at:
>
> https://drive.google.com/drive/folders/1z_giKv3QIUbYvSNOiTtMMr644v-wOG_k
>
> and builds in playground from:
>
> https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/playground
>
> https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=playground&status=&user=Brian+Inglis&id=4119
>
> https://github.com/cygwin/scallywag/actions/runs/2239985902
>
> The jobs appear to fail because some checks fail and return non-zero status.
> Comparing checks between ciurrent and proposed releases and across
> x86/_64/CI jobs, there appear to be fewer failures despite more tests.
>
> All feedback is encouraged and gratefully received.
Thanks for picking up coreutils, which is not only by name a core
package.
I think this is at least worthy of a pink hippo ;)
Corinna
next prev parent reply other threads:[~2022-05-04 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 5:15 Brian Inglis
2022-05-04 7:49 ` Corinna Vinschen [this message]
2022-05-04 11:25 ` Jon Turney
2022-05-04 14:11 ` Brian Inglis
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=YnIwFm+EEqBZWD8r@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.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).