This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections]
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, Paul Fertser <fercerpav at gmail dot com>, gdb-patches at sourceware dot org, ktietz at redhat dot com
- Date: Wed, 12 Feb 2014 07:00:12 +0400
- Subject: Re: getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections]
- Authentication-results: sourceware.org; auth=none
- References: <20140209172855 dot GA27131 at host2 dot jankratochvil dot net> <1392033768-16793-1-git-send-email-fercerpav at gmail dot com> <831tzavrhw dot fsf at gnu dot org> <20140210170244 dot GO2320 at home dot lan> <83vbwmuaj8 dot fsf at gnu dot org> <20140210195758 dot GA16956 at host2 dot jankratochvil dot net> <20140211034157 dot GG5485 at adacore dot com> <20140211200456 dot GA22728 at host2 dot jankratochvil dot net>
Thinking out loud...
> What do you mean by "an announcement"? gdb-announce maling list (ml)?
> gdb ml? gdb-patches ml? gdb/NEWS entry?
I am not really sure - we don't really have a procedure we've agreed
on. At the very very least, I would send an email to the gdb@ mailing
list. Would it be too much noise if we sent to gdb-announce@, though?
Should we also mention that fact with a NEWS entry on the GDB website?
I think so.
> This mail thread you do not seem to consider a good enough
> announcement for host maintainer.
I don't think we have any maintainer for those ports. I think we're
really searching for an idea of the remaining number of users instead.
For some of them, I used to have access to machines running those OSes,
and so could be used as a resource. But not anymore.
Note that I'm also open to discussing a different strategy where
we could decide that for those very old and exotic platforms with
no maintainer and no recent activity, it's OK to just deprecate
the port without further ado.
I propose the following:
- Email to gdb or gdb-announce to announce that ports XXX, YYY, and
ZZZ are deprecated, and that GDB version 7.8 will be the last
release supporting them. The decision can be reverted if someone
commits to maintaining that port;
- Add corresponding note in GDB's website news area.
--
Joel