From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1
Date: Fri, 24 Feb 2017 03:18:00 -0000 [thread overview]
Message-ID: <58AFA559.6010404@cygwin.com> (raw)
In-Reply-To: <DM2PR0201MB079999334855BA9BB10EC9C2A7530@DM2PR0201MB0799.namprd02.prod.outlook.com>
On 02/23/2017 06:01 PM, Tony Kelman wrote:
>> The big question remains, where this speed boost coming from?
>> Is this a startup time? Or some internal slowness?
>> Because in latter case, given your STC, this is a bash issue and should be
>> reported upstream.
>
> Dunno what you meant by STC, but upstream is well aware:
>
> $ man bash | tail -n 21 | head -n 2
> BUGS
> It's too big and too slow.
Forgive me but this entire thread has been giving me a serious case of
deja-vu. We've been down a similar path to this before, the last time
around with "ash" rather than "dash" but the arguments sound very familiar.
Brian Dessent has a nice summary a paragraph into his response below:
https://sourceware.org/ml/cygwin/2008-03/msg00369.html
Now this was "ash" and not "dash" and the actual transition from "bash" to
"ash" and back again occurred well over 10 years ago, so allot of things
have changed for sure. But I bring this up because I think the parallels
are there. Since making a change of this magnitude is going to be an
undertaking, we should be sure we're going to see the intended benefits
before enduring the pain such a change would bring, though hopefully that
pain would be short-lived and/or minor. :-)
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-02-24 3:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 14:01 Eric Blake (cygwin)
2017-02-23 4:20 ` Steven Penny
2017-02-23 17:50 ` Andrey Repin
2017-02-23 19:46 ` Steven Penny
2017-02-23 19:59 ` Brian Inglis
2017-02-23 20:41 ` Eric Blake
2017-02-24 7:19 ` Yaakov Selkowitz
2017-02-23 23:44 ` Steven Penny
2017-02-24 14:32 ` Eric Blake
2017-02-24 19:19 ` Brian Inglis
2017-02-23 22:05 ` Andrey Repin
2017-02-23 23:01 ` Tony Kelman
2017-02-23 23:04 ` Eliot Moss
2017-02-23 23:12 ` Kenneth Wolcott
2017-02-23 23:30 ` Vince Rice
2017-02-23 23:35 ` Andrey Repin
2017-02-24 3:16 ` Larry Hall (Cygwin)
2017-02-24 3:18 ` Larry Hall (Cygwin) [this message]
2017-02-24 4:57 ` Steven Penny
2017-02-24 14:43 ` Eric Blake
2017-02-24 15:05 ` Lee Dilkie
2017-02-25 16:55 ` Steven Penny
2017-03-01 23:57 ` Matt Seitz (matseitz)
2017-02-23 23:33 ` Steven Penny
2017-02-25 16:46 ` cyg Simple
2017-02-25 17:09 ` Steven Penny
2017-02-27 10:20 ` Csaba Raduly
2017-02-27 12:48 ` Steven Penny
2017-02-27 23:13 ` Duncan Roe
2017-02-28 0:51 ` Steven Penny
2017-02-28 20:52 ` cyg Simple
2017-02-28 21:43 ` Steven Penny
2017-03-01 14:42 ` cyg Simple
2017-03-02 0:22 ` Steven Penny
2017-03-02 3:46 ` Vince Rice
2017-03-02 5:27 ` Steven Penny
2017-03-02 5:31 ` Vince Rice
2017-03-02 12:36 ` Steven Penny
2017-03-02 13:37 ` Marco Atzeri
2017-03-02 14:29 ` Eric Blake
2017-03-02 16:16 ` Nellis, Kenneth (Conduent)
2017-03-02 17:28 ` Brian Inglis
2017-03-02 18:45 ` Eric Blake
2017-03-02 23:23 ` Brian Inglis
2017-03-02 18:28 ` Achim Gratz
2017-03-02 14:31 ` Brian Inglis
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=58AFA559.6010404@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--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).