From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8751 invoked by alias); 24 Jan 2002 16:59:22 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 8717 invoked from network); 24 Jan 2002 16:59:21 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 24 Jan 2002 16:59:21 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id DD93C3D8C for ; Thu, 24 Jan 2002 11:59:19 -0500 (EST) Message-ID: <3C503D67.7080702@cygnus.com> Date: Thu, 24 Jan 2002 08:59:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: [rfc] maint note on obsoleting code Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00284.txt.bz2 In doing 5.1.1 (not my day) and further updating how-to-release I'm thinking of adding the following under ``Obsoleting targets and code''. @emph{Maintainer note: Obsoleting a target or code is actually a good thing. Firstly it helps the developers by removing code that is either no longer relevant or simply wrong. Secondly since it removes any history associated with the file (effectively clearing the slate) the developer has a much freer hand when it comes to fixing broken files.} Does anyone have a better way of expressing this sentiment? Andrew