From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Regression (last snapshot)
Date: Sun, 21 Jul 2019 09:42:00 -0000 [thread overview]
Message-ID: <c7f82026d0bd390906f0792cf76cc141@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <f2674a4f34ad3c5c30d6556a35bcd3ff@smtp-cloud8.xs4all.net>
On Sun, 21 Jul 2019 11:38:49, Houder wrote:
> On Sun, 21 Jul 2019 00:55:51, Houder wrote:
> > L.S.,
> >
> > Using the latest snapshot, I now get a complaint from 'ls'; this does
> > not happen w/ 3.0.7
> >
> > Henri
> >
> > = 3.0.7:
> >
> > 64-@@ uname -a
> > CYGWIN_NT-6.1 Seven 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 Cygwin
> >
> > 64-@@ ls -lL <(grep bash .bashrc)
> > pr-------- 1 Henri None 0 Jul 21 00:49 /dev/fd/63
> >
> > = snapshot 2019-07-12:
> >
> > 64-@@ uname -a
> > CYGWIN_NT-6.1 Seven 3.1.0s(0.339/5/3) 2019-07-12 15:28 x86_64 Cygwin
> >
> > 64-@@ ls -lL <(grep bash .bashrc)
> > ls: /dev/fd/63: No such file or directory
> > pr-------- 1 Henri None 0 Jul 21 00:41 /dev/fd/63
>
> However 32-bits Cygwin does not complain ...
Sorry, my mistake (32-bits also complains)
@@ uname -a
CYGWIN_NT-6.1-WOW Seven 3.1.0s(0.339/5/3) 2019-07-12 15:28 i686 Cygwin
@@ ls -lL <(grep bash .bashrc)
ls: /dev/fd/63: No such file or directory
pr-------- 1 Henri None 0 Jul 21 11:41 /dev/fd/63
=====
--
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:[~2019-07-21 9:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 22:55 Houder
2019-07-21 9:38 ` Houder
2019-07-21 9:42 ` Houder [this message]
2019-07-22 12:23 ` Ken Brown
2019-07-22 13:44 ` Ken Brown
2019-07-22 15:20 ` Corinna Vinschen
2019-07-22 15:53 ` Corinna Vinschen
2019-07-22 16:45 ` Corinna Vinschen
2019-07-22 18:47 ` Houder
2019-07-26 22:12 ` Ken Brown
2019-07-27 0:14 ` Ken Brown
2019-07-27 10:21 ` Houder
2019-07-27 15:24 ` Ken Brown
2019-07-27 16:25 ` Houder
2019-07-29 8:45 ` Corinna Vinschen
2019-07-29 13:18 ` Ken Brown
2019-07-29 13:35 ` Ken Brown
2019-07-29 13:48 ` Corinna Vinschen
2019-07-29 13:47 ` Corinna Vinschen
2019-07-29 14:26 ` Ken Brown
2019-07-29 15:23 ` Corinna Vinschen
2019-07-29 15:40 ` Corinna Vinschen
2019-07-29 18:56 ` Ken Brown
2019-07-31 15:53 ` Ken Brown
2019-07-31 18:00 ` Ken Brown
2019-08-01 9:01 ` Corinna Vinschen
2019-08-01 14:27 ` Jon Turney
2019-08-01 15:30 ` Ken Brown
2019-08-01 15:38 ` Eric Blake
2019-08-01 16:04 ` Corinna Vinschen
2019-08-01 21:17 ` Ken Brown
2019-08-02 2:32 ` Ken Brown
2019-08-02 14:34 ` Ken Brown
2019-08-02 15:04 ` Corinna Vinschen
2019-08-02 21:26 ` Brian Inglis
2019-08-02 21:53 ` Ken Brown
2019-08-02 21:58 ` Eric Blake
2019-08-03 3:50 ` Brian Inglis
2019-08-03 13:14 ` Ken Brown
2019-08-04 16:52 ` Houder
2019-08-01 10:03 ` Houder
2019-08-01 10:46 ` Houder
2019-08-01 12:20 ` Ken Brown
2019-08-01 14:29 ` Houder
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=c7f82026d0bd390906f0792cf76cc141@smtp-cloud8.xs4all.net \
--to=houder@xs4all.nl \
--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).