From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5130 invoked by alias); 16 Jul 2002 23:30:40 -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 5122 invoked from network); 16 Jul 2002 23:30:39 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 16 Jul 2002 23:30:39 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 6F2C4D2CBD; Tue, 16 Jul 2002 16:30:39 -0700 (PDT) Date: Tue, 16 Jul 2002 16:59:00 -0000 From: Joel Brobecker To: Elena Zannoni Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] unneeded extra brace in infrun.c (handle_inferior_event) Message-ID: <20020716233039.GG2700@gnat.com> References: <20020716204432.GE2700@gnat.com> <15668.35195.754595.953902@localhost.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15668.35195.754595.953902@localhost.redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2002-07/txt/msg00358.txt.bz2 > I vote for reindenting the code. Infrun.c has been on the quiet side > for a bit, and I don't think this change will cause any problems. I can do the following, all within a short period: - remove the braces (without indentation change) - commit - run gdb_indent.sh - commit That way, we have one commit which contains a code change, but the diff is readable. The second diff may be unreadable, but will contain no code change. Should I go ahead? -- Joel