From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gnulib: import getline
Date: Sun, 2 May 2021 11:12:34 -0400 [thread overview]
Message-ID: <YI7BYgMLU3mi9cNv@vapier> (raw)
In-Reply-To: <83pmy96vkb.fsf@gnu.org>
On 02 May 2021 17:48, Eli Zaretskii wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > On 02 May 2021 10:14, Eli Zaretskii wrote:
> > > From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
> > > > getline is in POSIX, but not all targets support it. e.g. Windows
> > > > (mingw) omit it.
> > >
> > > Which MinGW? mingw.org's MinGW does have getline and getdelim.
> >
> > mingw.org doesn't exist anymore
>
> Of course it does.
if you mean it as a project name and not a domain name, OK. if you mean
as a domain name, then no, it does not. it's a domain squatter.
> > and sf.net/p/mingw hasn't been updated in almost a decade.
>
> That's a stale URL. The up-to-date one is here:
>
> https://osdn.net/projects/mingw/releases/
>
> The latest release was on April 12.
the project needs to get its act together then and setup redirects. the
SF page is the top search results and people are still going there, and
it's seeing tons of downloads per week from it.
> > we switched to http://mingw-w64.org/ for 64-bit support.
>
> That's fine, but for 32-bit code they are not the only game in town.
ok, but there's not a lot of value in a dying platform. if the project
doesn't support 64-bit, then it's of limited value.
-mike
next prev parent reply other threads:[~2021-05-02 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 22:09 Mike Frysinger via Gdb-patches
2021-05-02 0:39 ` Simon Marchi via Gdb-patches
2021-05-02 0:46 ` Mike Frysinger via Gdb-patches
2021-05-02 0:49 ` Simon Marchi via Gdb-patches
2021-05-02 4:50 ` Mike Frysinger via Gdb-patches
2021-05-04 15:03 ` Tom Tromey
2021-05-04 17:46 ` Mike Frysinger via Gdb-patches
2021-05-04 19:19 ` Tom Tromey
2021-05-04 19:49 ` Mike Frysinger via Gdb-patches
2021-05-04 20:10 ` Tom Tromey
2021-05-04 21:22 ` Mike Frysinger via Gdb-patches
2021-05-02 7:14 ` Eli Zaretskii via Gdb-patches
2021-05-02 14:14 ` Mike Frysinger via Gdb-patches
2021-05-02 14:48 ` Eli Zaretskii via Gdb-patches
2021-05-02 15:12 ` Mike Frysinger via Gdb-patches [this message]
2021-05-02 15:24 ` Eli Zaretskii via Gdb-patches
2021-05-02 15:47 ` Mike Frysinger via Gdb-patches
2021-05-02 16:06 ` Eli Zaretskii via Gdb-patches
2021-05-02 16:12 ` Mike Frysinger via Gdb-patches
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=YI7BYgMLU3mi9cNv@vapier \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=vapier@gentoo.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