From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7823 invoked by alias); 12 Apr 2012 15:20:34 -0000 Received: (qmail 7783 invoked by uid 22791); 12 Apr 2012 15:20:30 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 12 Apr 2012 15:19:09 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q3CFJ85x008682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 12 Apr 2012 11:19:09 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q3CFJ7hx031284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Apr 2012 11:19:08 -0400 From: Tom Tromey To: Sergio Durigan Junior Cc: Jan Kratochvil , gdb-patches@sourceware.org Subject: Re: [patch] More suggestive error_is_running message References: <20120410191907.GA31331@host2.jankratochvil.net> <20120411005611.GA10986@host2.jankratochvil.net> Date: Thu, 12 Apr 2012 15:28:00 -0000 In-Reply-To: (Sergio Durigan Junior's message of "Tue, 10 Apr 2012 23:16:19 -0300") Message-ID: <87lim10yhg.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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 X-SW-Source: 2012-04/txt/msg00304.txt.bz2 Sergio> In such cases I never know if those new standards apply for new Sergio> projects, or for existing projects as well. If they apply to existing Sergio> projects, then I'm not sure there should be any massive Sergio> replacement/adjustment in the codebase to reflect those new rules. I tend to think we should change, but it is a surprisingly tricky area. Tom