public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ronald Landheer-Cieslak <blytkerchan@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: cygwin bash 2.05b patches and "rebash" a debugger for bash (http://bashdb.sourceforge.net)
Date: Fri, 12 Sep 2003 12:45:00 -0000	[thread overview]
Message-ID: <20030912131347.GK3362@linux_rln.harvest> (raw)
In-Reply-To: <16225.47261.577664.992869@panix3.panix.com>

On Fri, Sep 12, 2003 at 08:14:21AM -0400, R. Bernstein wrote:
>  > The Cygwin version is vanilla bash plus patches 001 to 004 plus the
>  > below patches:
> Actually, if you look here:
> 
>   http://ftp.gnu.org/pub/gnu/bash/bash-2.05b-patches/
> 
> you'll see that there are 3 more from March of this year. The
> rebash/bashdb CVS sources have these applied as well. Some of the
> fixes from Debian are also probably worth applying as some of them
> aren't necessarily specific to Debian. These would be in the db
> directory in CVS. 
> 
> And last, but certainly not least, is that issue of coordinating
> patches between cygwin and rebash/bashdb.
The patches that have not been applied yet will be applied in the next
release. 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 :)

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. You'll
be able to get them from the source tarball at every release.

rlc

-- 
You roll my log, and I will roll yours.
		-- Lucius Annaeus Seneca

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

  reply	other threads:[~2003-09-12 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 14:54 R. Bernstein
2003-09-11 15:23 ` Corinna Vinschen
2003-09-11 20:50   ` R. Bernstein
2003-09-12 11:31     ` Corinna Vinschen
2003-09-12 12:14       ` R. Bernstein
2003-09-12 12:45         ` Ronald Landheer-Cieslak [this message]
2003-09-12 14:13           ` R. Bernstein
2003-09-12 14:48             ` Ronald Landheer-Cieslak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030912131347.GK3362@linux_rln.harvest \
    --to=blytkerchan@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).