From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13328 invoked by alias); 10 Sep 2014 16:00:16 -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 13300 invoked by uid 89); 10 Sep 2014 16:00:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 10 Sep 2014 16:00:13 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s8AG08Ah027339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 10 Sep 2014 12:00:08 -0400 Received: from localhost (dhcp-10-15-16-169.yyz.redhat.com [10.15.16.169]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s8AG04lk029636 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Wed, 10 Sep 2014 12:00:06 -0400 From: Sergio Durigan Junior To: Joel Brobecker Cc: Pedro Alves , Ulrich Weigand , GDB Patches Subject: Re: eliminate deprecated_insert_raw_breakpoint. what's left. References: <201409101445.s8AEjILM007935@d06av02.portsmouth.uk.ibm.com> <54106C61.7040400@redhat.com> <20140910155028.GQ28404@adacore.com> X-URL: http://www.redhat.com Date: Wed, 10 Sep 2014 16:00:00 -0000 In-Reply-To: <20140910155028.GQ28404@adacore.com> (Joel Brobecker's message of "Wed, 10 Sep 2014 08:50:28 -0700") Message-ID: <87d2b3lb3w.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2014-09/txt/msg00330.txt.bz2 On Wednesday, September 10 2014, Joel Brobecker wrote: > So let's discuss the new obsoleting procedure, so we can document it: > > . I think that the first 4 steps (post email on gdb@, wait a week, > then on gdb-announce, wait another week) are fine. Anyone thinks > we should go straight to gdb-announce? > > My thinking is that people interested in maintaining a port > with enough skills to do so are likely to already be on gdb@, > so we can avoid sending an extra mail to gdb-announce. But > the traffic on gdb-announce being very low, and the frequency > at which we deprecate targets being fairly small as well, > I wouldn't object to a simpler procedure where we email > gdb-announce directly. Not sure if it is implicit, but it would be good to send an email to gdb-patches as well. I have a feeling that some people just read/pay attention to gdb-patches... Other than that, I totally agree with the plan. Cheers, -- Sergio GPG key ID: 0x65FC5E36 Please send encrypted e-mail if possible http://sergiodj.net/