Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Richard.Earnshaw@arm.com, simark@simark.ca, tom@tromey.com,
	tdevries@suse.de, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Use PyConfig for python 3.9
Date: Wed, 12 Nov 2025 20:20:38 +0200	[thread overview]
Message-ID: <86o6p7ru2x.fsf@gnu.org> (raw)
In-Reply-To: <867bvvxh62.fsf@aarsen.me> (message from Arsen =?utf-8?Q?Arse?= =?utf-8?Q?novi=C4=87?= on Wed, 12 Nov 2025 19:03:01 +0100)

> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: "Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>,  simark@simark.ca,
>   tom@tromey.com,  tdevries@suse.de,  gdb-patches@sourceware.org
> Date: Wed, 12 Nov 2025 19:03:01 +0100
> 
> I think that, for Windows XP, the repetition of this conversation any
> time someone wants to use something that doesn't work on XP is reason
> enough to remove it.
> 
> It's a proprietary OS even its vendor abandoned 11 years ago.  The
> milliwatts spent composing this email are enough to justify ignoring it
> further.

If we are going that low in our discussion level, then I submit that
you could have easily avoided the waste of those milliwatts by not
writing that email.

Seriously, do you really believe this level of discussion, with the
implied quite apparent hostility, is something that should have place
here?  It's unbecoming.

> Frankly, a Windows XP machine that has enough networking hardware to
> download the next release of GDB is likely a massive liability in the
> first place.  Hopefully none are still connected to the internet.

There are still a lot of systems running XP in the world.  So not
dropping support of XP has some advantages for our users, not just
disadvantages.  The GNU Project, being a Free Software project, has
the advantage of not following the lead of the likes of Microsoft in
our decisions whether or not we want to help people who use those
systems.  I thought it was evident, perhaps even perceived as a
virtue, but maybe not.

  reply	other threads:[~2025-11-12 18:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 13:36 Tom de Vries
2025-10-17 14:13 ` Tom Tromey
2025-10-17 15:11   ` Eli Zaretskii
2025-10-17 16:33     ` Tom Tromey
2025-10-17 18:34       ` Eli Zaretskii
2025-10-31 18:15         ` Tom Tromey
2025-11-01  7:00           ` Eli Zaretskii
2025-11-03 17:09             ` Simon Marchi
2025-11-03 18:21               ` Eli Zaretskii
2025-11-12 16:52                 ` Richard Earnshaw (foss)
2025-11-12 17:23                   ` Eli Zaretskii
2025-11-12 17:53                     ` Richard Earnshaw (foss)
2025-11-12 18:03                     ` Arsen Arsenović
2025-11-12 18:20                       ` Eli Zaretskii [this message]
2025-11-12 19:24                         ` Arsen Arsenović
2025-11-13  5:45                           ` Eli Zaretskii
2025-10-17 16:51     ` Arsen Arsenović
2025-10-17 18:35       ` Eli Zaretskii

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=86o6p7ru2x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Richard.Earnshaw@arm.com \
    --cc=arsen@aarsen.me \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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