From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10637 invoked by alias); 26 Feb 2012 23:09:43 -0000 Received: (qmail 10629 invoked by uid 22791); 26 Feb 2012 23:09:42 -0000 X-SWARE-Spam-Status: No, hits=1.0 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,TW_DJ,TW_GP,TW_JG X-Spam-Check-By: sourceware.org Received: from mpv2.tis.CWRU.Edu (HELO mpv2.tis.cwru.edu) (129.22.105.37) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 26 Feb 2012 23:09:28 +0000 Received: from mpv8.case.edu (mpv8.tis.cwru.edu [129.22.105.116]) by mpv2.tis.cwru.edu (MOS 4.3.3-GA) with ESMTP id BIL27788; Sun, 26 Feb 2012 18:09:27 -0500 Received: from h49.189.190.173.dynamic.ip.windstream.net (EHLO z4.local) ([173.190.189.49]) by mpv8.case.edu (MOS 4.3.3-GA FastPath queued) with ESMTP id SYF27080 (AUTH cpr); Sun, 26 Feb 2012 18:09:26 -0500 (EST) Message-ID: <4F4ABBA4.4050000@case.edu> Date: Mon, 27 Feb 2012 03:55:00 -0000 From: Chet Ramey Reply-To: chet.ramey@case.edu User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Pierre Muller CC: "'Pedro Alves'" , bug-readline@gnu.org, gdb-patches@sourceware.org, chet.ramey@case.edu Subject: Re: [Bug-readline] PING [RFA] Fix djgpp gdb-7.4 (and probably trunk) build failure in readline References: <008101ccdde8$d71f84e0$855e8ea0$@muller@ics-cnrs.unistra.fr> <4f479be7.0610440a.3c16.080cSMTPIN_ADDED@mx.google.com> <4F479FE9.4060408@redhat.com> <4F49395E.4020904@case.edu> <4f4943b8.c14eb40a.5ca7.7035SMTPIN_ADDED@mx.google.com> In-Reply-To: <4f4943b8.c14eb40a.5ca7.7035SMTPIN_ADDED@mx.google.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Junkmail-Whitelist: YES (by domain whitelist at mpv2.tis.cwru.edu) 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-02/txt/msg00622.txt.bz2 On 2/25/12 3:07 PM, Pierre Muller wrote: >> The fix is already in the mainline readline source, though in a different >> form. I don't want to hold your release up waiting for the readline >> release process, hence my recommendation that you move forward with the >> patch in its current form. > > I searched for this mainline readline source, but couldn't find the > location... > Is this accessible via cvs,svn, git or anything else, > or is it just private? The git repository for the distribution sources is available on savannah. There doesn't seem to be much to be gained by maintaining a `devel' branch for readline, since all of the source code changes are captured in the `devel' bash branch in its savannah git tree. I try to update the bash devel branch at least every month with the weekly snapshots. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/