public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: coreutils refresh request (again)
Date: Wed, 10 Jun 2020 18:24:15 +0000	[thread overview]
Message-ID: <DM6PR09MB40432C69723E46A203AF2915A5830@DM6PR09MB4043.namprd09.prod.outlook.com> (raw)

> but it is missing the patch used to adapt it to Cygwin.
> The patch modifies 27 files and unfortunately does not applies
> clean to latest upstream source.

Fair enough (and again, there was no pushing);  but are you sure that all 27 patches are still actual?

Testsuite ran pretty well, though.  I looked as some failures (not all), and they looked rather benign.

============================================================================
Testsuite summary for GNU coreutils 8.32
============================================================================
# TOTAL: 621
# PASS:  413
# SKIP:  167
# XFAIL: 0
# FAIL:  33
# XPASS: 0
# ERROR: 8

> The are at lest 3 points that need rewriting

Okay;  maybe those should be reported upstream, as Cygwin is largely standard-compliant these days?


             reply	other threads:[~2020-06-10 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 18:24 Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2020-06-10 18:58 ` Marco Atzeri
  -- strict thread matches above, loose matches on Subject: below --
2020-06-10 16:21 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 16:46 ` Marco Atzeri
2020-06-10 21:26 ` Brian Inglis
2020-05-31 14:52 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-04 13:56 ` 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=DM6PR09MB40432C69723E46A203AF2915A5830@DM6PR09MB4043.namprd09.prod.outlook.com \
    --to=lavr@ncbi.nlm.nih.gov \
    --cc=cygwin@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).