Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: "Hans Horn" <hannes@2horns.com>
Subject:  Re: maintaining bash
Date:  Sun, 10 Apr 2005 10:14:34 -0700
Lines: 33
Message-ID: <d3bmoq$ji3$1@sea.gmane.org>
References:  <423AE723.3090801@buddydog.org> <6.1.2.0.0.20050318073557.01f85cc0@imap.myrealbox.com> <d348aa$6r6$1@sea.gmane.org> <4255B3C7.9030306@buddydog.org> <4255B8AC.2C88CDE6@dessent.net> <d34i0v$hdk$1@sea.gmane.org> <20050408022027.GB10856@trixie.casa.cgf.cx>

Folks,


> If you are still willing then you've got the job.
Alright, I'm on - despite a rough start!


> There is one potential problem in that we may need to adapt Pierre's
> patch to prevent problems with pid reuse to 3.0 if it is released.
How do I go about Pierre's pid patch?


> The next step is to create a package and offer it on the cygwin-apps 
> mailing list.
> Please look at the archives for examples of how this is done.
I'm a total virgin at this. I'm afraid I need help, professional help!
Right now I'm looking at http://cygwin.com/setup.html, as well as what ships 
with the binary and source distribution of the current cygwin bash.
Looks like bash2.x install in /usr/bin while bash3.x installs in 
/usr/local/bin. Is that ok?


As to Andrew Schulman's complaint about the "extra-space-after-the-prompt" 
bug (http://sources.redhat.com/ml/cygwin/2005-04/msg00325.html, first 
reported at http://mail-index.netbsd.org/pkgsrc-bugs/2005/03/25/0002.html), 
I believe to have fixed the problem. How do I about getting this fix (if we 
conclude that it is indeed working) back into mainstream bash?


greets,
H. 


--
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/