From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: palves@redhat.com, jan.kratochvil@redhat.com,
gdb-patches@sourceware.org, ktietz@redhat.com,
fercerpav@gmail.com
Subject: Re: [PATCH] Add IPv6 support for remote TCP connections
Date: Mon, 23 Mar 2015 19:18:00 -0000 [thread overview]
Message-ID: <83h9tbr09w.fsf@gnu.org> (raw)
In-Reply-To: <20150323191232.GI5438@adacore.com>
> Date: Mon, 23 Mar 2015 12:12:32 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Pedro Alves <palves@redhat.com>, jan.kratochvil@redhat.com, gdb-patches@sourceware.org, ktietz@redhat.com, fercerpav@gmail.com
>
> > What about developing on latest versions of Windows, but debugging on
> > Windows 9X? There could be 9X-specific problems that might require
> > that. (I had such an experience with Emacs about 3 years ago, and the
> > person who helped me debug the problem was using GDB 7.2 on a Windows
> > 98 box.)
>
> The problem is whether we have the means to support those older versions.
> I can help with XP, for instance, but not with 98. You also need to have
> people who are publicly committed to helping with the port's maintenance,
> as it's unfair IMO to ask anyone to worry about a platform that only
> affects 0.01%. Thinking from our perspective, we get more bang for our
> buck if we dedicate what resources we have to platforms that have more
> people using them.
Yes, this is all well-known. However, I thought the issue was a bit
different: not whether we want to spend efforts on active support of
these platforms, but rather whether we should try to avoid
deliberately breaking them by introducing features that are not
available there, and leaving no fallbacks for when those new features
are unavailable.
next prev parent reply other threads:[~2015-03-23 19:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:54 Paul Fertser
2014-02-09 8:31 ` Jan Kratochvil
2014-02-09 9:53 ` Paul Fertser
2014-02-09 13:05 ` Jan Kratochvil
2014-02-09 16:35 ` Eli Zaretskii
2014-02-09 16:47 ` Jan Kratochvil
2014-02-09 17:08 ` Paul Fertser
2014-02-09 17:29 ` Jan Kratochvil
[not found] ` <1392033768-16793-1-git-send-email-fercerpav@gmail.com>
2014-02-10 16:53 ` [PATCH v2] " Eli Zaretskii
2014-02-10 17:02 ` Paul Fertser
2014-02-10 17:45 ` Eli Zaretskii
2014-02-10 19:58 ` getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections] Jan Kratochvil
2014-02-11 3:42 ` Joel Brobecker
2014-02-11 20:05 ` Jan Kratochvil
2014-02-11 20:33 ` Stan Shebs
2014-02-12 3:04 ` Joel Brobecker
2014-02-12 3:00 ` Joel Brobecker
2014-02-12 12:10 ` Jan Kratochvil
2014-02-13 7:37 ` Joel Brobecker
2014-02-13 10:44 ` [patch] [sim] --disable-sim on ppc* by default (for AIX) [Re: getaddrinfo available on all GDB hosts?] Jan Kratochvil
2014-02-13 10:51 ` Pedro Alves
2014-02-13 11:04 ` Jan Kratochvil
2014-02-13 11:39 ` Pedro Alves
2014-02-13 11:51 ` Joel Brobecker
2014-02-13 12:08 ` [cancel] " Jan Kratochvil
2014-02-13 11:59 ` Joel Brobecker
2014-02-13 14:26 ` getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections] Tom Tromey
2014-02-13 11:36 ` Jan Kratochvil
2014-02-13 11:55 ` Joel Brobecker
2014-02-11 19:48 ` [PATCH v3] Add IPv6 support for outgoing remote TCP connections Paul Fertser
2014-02-12 16:53 ` Jan Kratochvil
2014-02-12 17:32 ` Paul Fertser
2014-02-12 20:10 ` Jan Kratochvil
2015-03-22 16:39 ` [PATCH] Add IPv6 support for " Jan Kratochvil
2015-03-22 16:54 ` Eli Zaretskii
2015-03-22 17:09 ` Jan Kratochvil
2015-03-22 17:48 ` Eli Zaretskii
2015-03-23 18:02 ` Pedro Alves
2015-03-23 18:42 ` Eli Zaretskii
2015-03-23 19:12 ` Joel Brobecker
2015-03-23 19:18 ` Eli Zaretskii [this message]
2015-04-13 15:12 ` Pedro Alves
2015-04-13 15:27 ` Eli Zaretskii
2015-04-13 16:10 ` Pedro Alves
2015-03-23 19:19 ` Pedro Alves
2015-03-23 19:03 ` Corinna Vinschen
2015-03-23 19:12 ` Pedro Alves
2014-02-09 16:29 ` Eli Zaretskii
2014-02-09 16:25 ` 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=83h9tbr09w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=fercerpav@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ktietz@redhat.com \
--cc=palves@redhat.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