bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new bug introduced by 'devel' commit 35bc7025c1db5078eb157eea7c04367


From: Chet Ramey
Subject: Re: new bug introduced by 'devel' commit 35bc7025c1db5078eb157eea7c0436754ac91aa3
Date: Thu, 13 May 2021 15:04:07 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.1

On 5/13/21 11:07 AM, Adjudicator Darren wrote:
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, May 13, 2021 5:02 PM, Chet Ramey <chet.ramey@case.edu> wrote:

On 5/13/21 10:31 AM, Adjudicator Darren wrote:

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, May 13, 2021 4:25 PM, Chet Ramey chet.ramey@case.edu wrote:

On 5/13/21 9:11 AM, Adjudicator Darren wrote:

What's the bug? this:

It's a work in progress.

I would use the master branch but apparently there are certain old things that 
only exist on 'devel' branch and so my old patches won't apply on 'master'.

What does this mean? The devel branch is always newer than master.

Would you recommend that I avoid 'devel' anyway?

The devel branch is what it claims to be: the development work on bash. If
you want to use it -- and I encourage people to use it to find bugs as we
go along -- you have to accept occasional instability. I appreciate you
using it and reporting this.

Right now, the devel branch is undergoing a series of multiple commits to
fix issues with array subscript expansion. That's what I mean about a work
in progress.

Understood. Thank you for the clarity.
For some reason I expected no instability(my bad), but I can see now why that 
was unreasonable of me, after all it is all in the name: 'devel'.

The latest push to the devel branch has a fix for this.


--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]