From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11758 invoked by alias); 3 Jul 2005 22:13:23 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 11731 invoked by uid 22791); 3 Jul 2005 22:13:19 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 03 Jul 2005 22:13:19 +0000 Received: from farnswood.snap.net.nz (p25-tnt2.snap.net.nz [202.124.108.25]) by viper.snap.net.nz (Postfix) with ESMTP id 81AC35BAB7E; Mon, 4 Jul 2005 10:13:15 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id DAC7962A9A; Sun, 3 Jul 2005 23:01:36 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17096.24639.940089.355645@farnswood.snap.net.nz> Date: Sun, 03 Jul 2005 22:13:00 -0000 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] Removal of markup annotations In-Reply-To: <20050703190449.GJ13811@nevyn.them.org> References: <17071.40307.949193.158796@farnswood.snap.net.nz> <20050703190449.GJ13811@nevyn.them.org> X-SW-Source: 2005-07/txt/msg00032.txt.bz2 > > This patch cleans up the code quite considerably and hopefully will relieve > > some of the pressure to remove the remaining annotations. > > Is there "pressure"? I don't see the point in snipping out bits of > -annotate=2 until we're ready to remove it entirely, which I would like > to do but I accept that we are not yet ready for. Its hard for me to tell if the pressure is real or imagined. There _was_ pressure two years ago (around Jan 2002) but the people involved aren't currently active on the mailing list. The idea behind level 3 annotations _was_ to allow snipping out a (large) bit of the sprinkled code for annotations. Its not a problem for me. If its not a problem for anyone else, then it might as well stay (although that does beg the question as to why it needs to be removed at all). Nick