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 Date: Thu, 7 Apr 2005 22:20:27 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: maintaining bash Message-ID: <20050408022027.GB10856@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <423AE723 DOT 3090801 AT buddydog DOT org> <6 DOT 1 DOT 2 DOT 0 DOT 0 DOT 20050318073557 DOT 01f85cc0 AT imap DOT myrealbox DOT com> <4255B3C7 DOT 9030306 AT buddydog DOT org> <4255B8AC DOT 2C88CDE6 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Thu, Apr 07, 2005 at 05:10:14PM -0700, Hans Horn wrote: >Nevermind! Sorry, folks - I really didn't mean to upset anybody! Bye then! No, no. Please. We are looking for a new bash maintainer. We haven't heard from the maintainer in a while and private email to him bounces. That is what prompted this message: http://sources.redhat.com/ml/cygwin-apps/2005-03/msg00005.html If you are willing to (actively) maintain bash it will be appreciated. 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. If you are still willing then you've got the job. 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. cgf -- 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/