From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31974 invoked by alias); 26 Feb 2003 16:57:02 -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 31967 invoked from network); 26 Feb 2003 16:57:02 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 172.16.49.205 with SMTP; 26 Feb 2003 16:57:02 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id h1QGv1Q27270; Wed, 26 Feb 2003 10:57:01 -0600 Date: Wed, 26 Feb 2003 16:57:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200302261657.h1QGv1Q27270@duracef.shout.net> To: gdb-patches@sources.redhat.com, kewarken@qnx.com Subject: Re: [Patch] correctly configure wcwidth in readline X-SW-Source: 2003-02/txt/msg00710.txt.bz2 Hi Kris, > What is the procedure for regenerating configure scripts? > Should I regenerate it here and commit it or do you have a certain person > who does it under a specific environment? I just finished my first configure patch so I just went through this. You should build autoconf 2.13 from ftp.gnu.org and use that to regenerate 'configure'. Diff 'configure' afterwards to make sure that the only differences are the changes you made + a couple of thousand lines of silly line-number differences. Don't include the configure diffs in your patch message, but do check them into CVS when you commit. As far as the patch goes, it's up to Elena Z to say what to do. I'll volunteer to help out if she would like. Michael C