From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: newlib@sourceware.org
Cc: cygwin@cygwin.com
Subject: Re: strverscmp is buggy in newlib 4.4.0 (was: Cygwin 3.4.6)
Date: Tue, 2 Jan 2024 14:28:16 -0700 [thread overview]
Message-ID: <ef3d8337-7b76-4d25-a300-7c13ff54de40@SystematicSW.ab.ca> (raw)
In-Reply-To: <1052086998.4232956.1704227350804@mail.yahoo.com>
On 2024-01-02 13:29, matthew patton via Cygwin wrote:
>> The cause is apparently that Cygwin's strverscmp implementation wasborrowed from musl libc
> would it make sense to use git submodules when "borrowing" code so the
> upstream reference is not lost, and keeping it abreast is relatively trivial
> exercise?
Issue is in newlib (x-post and followups set):
https://sourceware.org/cgit/newlib-cygwin/tree/newlib/libc/string/strverscmp.c
Docs for man pages are embedded in newlib (but not Cygwin unfortunately)
sources, but it would be nice if folks added a subsection or reference with
{Free,Open,Net}BSD/musl/etc. links, so we could see where and when the code was
copied, although some sources include BSD revision headers and copyrights, other
sources have no identifying header.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2024-01-02 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13421190.uLZWGnKmhe@nimes>
2024-01-02 17:36 ` Brian Inglis
2024-01-04 12:28 ` strverscmp is buggy in newlib 4.4.0 (was " Brian Inglis
2024-01-08 12:16 ` Corinna Vinschen
[not found] ` <1052086998.4232956.1704227350804@mail.yahoo.com>
2024-01-02 21:28 ` Brian Inglis [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=ef3d8337-7b76-4d25-a300-7c13ff54de40@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=newlib@sourceware.org \
/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).