Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "R. Bernstein" <rocky AT panix DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16224.57356.609720.972967@panix3.panix.com>
Date: Thu, 11 Sep 2003 16:50:20 -0400
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bash 2.05b patches and "rebash" a debugger for bash (http://bashdb.sourceforge.net)
In-Reply-To: <20030911152028.GV9981@cygbert.vinschen.de>
References: <16224 DOT 32353 DOT 754787 DOT 145806 AT panix3 DOT panix DOT com>
	<20030911152028 DOT GV9981 AT cygbert DOT vinschen DOT de>
Reply-To: rocky AT panix DOT com

Corinna Vinschen writes:
 > Using the bash source package from the Cygwin distro might help.

The source does not contain patches or diffs. Are there patches stored
separately from source? What happens when a new release comes out?
(Debian patches are nicely bundled for each particular problem and can
be installed and uninstalled separately)

I can do a "diff -Naur" to get the diffs and try to sort out which
ones are specific to cygwin as opposed to general patches such as
those found in bash public patches, I was hoping however for maybe
some coordination here. 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/