From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19291 invoked by alias); 12 Feb 2014 03:00:17 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 19275 invoked by uid 89); 12 Feb 2014 03:00:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 12 Feb 2014 03:00:15 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 9CAE311659F; Tue, 11 Feb 2014 22:00:13 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Zsdr1dSL13QY; Tue, 11 Feb 2014 22:00:13 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 506BA116584; Tue, 11 Feb 2014 22:00:11 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 46FF1E05F6; Wed, 12 Feb 2014 07:00:12 +0400 (RET) Date: Wed, 12 Feb 2014 03:00:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: Eli Zaretskii , Paul Fertser , gdb-patches@sourceware.org, ktietz@redhat.com Subject: Re: getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections] Message-ID: <20140212030012.GO5485@adacore.com> References: <20140209172855.GA27131@host2.jankratochvil.net> <1392033768-16793-1-git-send-email-fercerpav@gmail.com> <831tzavrhw.fsf@gnu.org> <20140210170244.GO2320@home.lan> <83vbwmuaj8.fsf@gnu.org> <20140210195758.GA16956@host2.jankratochvil.net> <20140211034157.GG5485@adacore.com> <20140211200456.GA22728@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140211200456.GA22728@host2.jankratochvil.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-02/txt/msg00376.txt.bz2 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