public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: coreutils refresh request (again)
Date: Wed, 10 Jun 2020 20:58:26 +0200	[thread overview]
Message-ID: <f55c53bb-64a3-c3a7-54d0-12f439b99525@gmail.com> (raw)
In-Reply-To: <DM6PR09MB40432C69723E46A203AF2915A5830@DM6PR09MB4043.namprd09.prod.outlook.com>

On 10.06.2020 20:24, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> 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?
> 

the testsuite is not relevant for these changes.

Coreutils are tweaked to manage "program" and "program.exe" as they
are the same thing and other similar things.
Some changes were propagated upstream and some not; I looked at the
first patch rejected, and upstream have reversed the logic of a test
that the patch was modifying to add one of these cases, so modifying the
source is not banal and need some consideration and test.

Both requires time that someone need to put for it.

Regards
Marco








  reply	other threads:[~2020-06-10 18:58 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]
2020-06-10 18:58 ` Marco Atzeri [this message]
  -- 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=f55c53bb-64a3-c3a7-54d0-12f439b99525@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).