Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16225.54401.128298.661226@panix3.panix.com> Date: Fri, 12 Sep 2003 10:13:21 -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: <20030912131347.GK3362@linux_rln.harvest> References: <16224 DOT 32353 DOT 754787 DOT 145806 AT panix3 DOT panix DOT com> <20030911152028 DOT GV9981 AT cygbert DOT vinschen DOT de> <16224 DOT 57356 DOT 609720 DOT 972967 AT panix3 DOT panix DOT com> <20030912113130 DOT GG9981 AT cygbert DOT vinschen DOT de> <16225 DOT 47261 DOT 577664 DOT 992869 AT panix3 DOT panix DOT com> <20030912131347 DOT GK3362 AT linux_rln DOT harvest> Reply-To: rocky AT panix DOT com This is all a bit too cryptic for me. Ronald Landheer-Cieslak writes: > The patches that have not been applied yet will be applied in the next > release. Whose release? If you are talking about a cygwin release, yes, I'd imagine one would want to put in public patches that are missing :-) Assuming you are talking about a cygwin release, is there a schedule for that? Aside from the 6-month-old public patches, is anything else currently planned? Is there a publically accessible CVS or cygwin-bash mailing list that one can track what's this other stuff might be? > As I don't use Debian (only RH8 and Gentoo) their patches will > have to wait until they're pushed up stream to vanilla Bash. > > OTOH, if you know about patches that might be interesting for Cygwin users, > then PTC will, of course, apply :) What's PTC? > > As for coordinating patches between Cygwin bash and your bash, you'll have > the patches applied in the source package, as I'll be using method #2. I'm lost as to what you are referring to. What's method #1 and what's method #2. > You'll > be able to get them from the source tarball at every release. You mean I can do a diff -Naur? Or are there patches available with the release from the previous release? As I wrote above, I find this a bit cryptic. It sort of sounds like you are saying that if I find any patches that I think might be useful for cygwin I should send them along and if I want figure out what changes cygwin has made to bash, I can diff the source whenever a release comes out. I was hoping for better 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/