From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Dash 0.5.10
Date: Sun, 26 May 2019 19:36:00 -0000 [thread overview]
Message-ID: <f47387d1-6529-ffcf-4f9b-3061b428b4d8@SystematicSw.ab.ca> (raw)
In-Reply-To: <5ceadd96.1c69fb81.93cbc.87fe@mx.google.com>
On 2019-05-26 12:40, Steven Penny wrote:
> I noticed a new Dash version is available since May 2018:
> http://gondor.apana.org.au/~herbert/dash/files
> Does the new version have some issue blocking Cygwin? If not can we publish
> new version?
Do you really need fixes in 0.5.10.2; looked at the number of bugs and patches
from then until February https://www.spinics.net/lists/dash/?
May be better to wait for the next release 0.5.11!
[Upstream maintainer @ RH seems to be busy getting Linux crypto up to V4.
Not that IBM being heavy into crypto and merging with RH may affect that!]
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2019-05-26 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 18:40 Steven Penny
2019-05-26 19:36 ` Brian Inglis [this message]
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=f47387d1-6529-ffcf-4f9b-3061b428b4d8@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).