From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22200 invoked by alias); 17 Jan 2012 19:56:08 -0000 Received: (qmail 22191 invoked by uid 22791); 17 Jan 2012 19:56:07 -0000 X-SWARE-Spam-Status: No, hits=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,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; Tue, 17 Jan 2012 19:55:55 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0HJts0w024922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 17 Jan 2012 14:55:54 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q0HJtsYk010912; Tue, 17 Jan 2012 14:55:54 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id q0HJtquP019202; Tue, 17 Jan 2012 14:55:53 -0500 From: Tom Tromey To: Jan Kratochvil Cc: gdb-patches@sourceware.org Subject: Re: [patch] New set auto-load-local-gdbinit + disable it by default References: <20120117095552.GA6141@host2.jankratochvil.net> Date: Tue, 17 Jan 2012 20:09:00 -0000 In-Reply-To: <20120117095552.GA6141@host2.jankratochvil.net> (Jan Kratochvil's message of "Tue, 17 Jan 2012 10:55:52 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (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-01/txt/msg00634.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> +* GDB no longer reads .gdbinit file from current directory by default. Jan> + Use "gdb -x .gdbinit" to retain the original behavior. I think the NEWS entry should also mention the new parameter. This is the simplest way for people to get back the old behavior; and anyway new parameters should always be mentioned in NEWS. Tom