From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23268 invoked by alias); 6 Aug 2013 16:35:40 -0000 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 Received: (qmail 23258 invoked by uid 89); 6 Aug 2013 16:35:40 -0000 X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 06 Aug 2013 16:35:39 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r76GZTPP019821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Aug 2013 12:35:30 -0400 Received: from host2.jankratochvil.net (ovpn-116-33.ams2.redhat.com [10.36.116.33]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r76GZQbq032553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 6 Aug 2013 12:35:28 -0400 Date: Tue, 06 Aug 2013 16:35:00 -0000 From: Jan Kratochvil To: mbilal Cc: palves@redhat.com, gdb-patches@sourceware.org Subject: Re: [PATCH 0/7] PR gdb/15224 should "set history save on" by default Message-ID: <20130806163525.GA28090@host2.jankratochvil.net> References: <51877A32.1030503@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51877A32.1030503@codesourcery.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2013-08/txt/msg00177.txt.bz2 On Mon, 06 May 2013 11:38:58 +0200, mbilal wrote: > Here is the proposed patch series of 'set history save on' by default > A thread has been discussed here > http://sourceware.org/ml/gdb-patches/2013-04/msg00067.html This was leading to getting accepted but there were too many threaded mails, it would be great if you could resubmit it as completely new mails (no replies), best a new mail for every patch part. Additionally a GIT branch for it would be even better but that is not required. Thanks, Jan