From: John Wiersba <John.Wiersba@medstat.com>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: cat broken
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <03F4742D8225D21191EF00805FE62B990205E180@AA-MSG-01> (raw)
Message-ID: <19990630221000.P235dc5ZXlnYQu7jgLzSF6_v6vie2YKwBgfaFKo3Ik8@z> (raw)
Actually, I tried a sample of the snapshots I found on
ftp://go.cygnus.com/pub/sourceware.cygnus.com/cygwin/snapshots/ from the
following list of dates:
0523 0524 0526 0528 0529 0530 0531 0601 0602 0603 0604 0605 0607 0608 0610
0612 0614 0615
I assumed that if it failed at the endpoints and also in the middle that it
failed everywhere. After reading your email, I thought maybe I'd go out and
try every one. It appears that the snapshot on 5/28 does *not* have the
fhandler_base::fork_fixup bug. Thanks for spurring me on!
Hopefully, 5/28 doesn't have any other new major bugs, either.
-- John
> -----Original Message-----
> From: Chris Faylor [ mailto:cygwin@sourceware.cygnus.com ]
> Sent: Thursday, June 24, 1999 3:13 PM
> To: John Wiersba
> Cc: cygwin users
> Subject: Re: cat broken
>
>
> On Thu, Jun 24, 1999 at 03:02:58PM -0400, John Wiersba wrote:
> >OK, then it appears that every snapshot since 5/24 has this
> bug in it. I'm
> >not exactly sure why it is showing up so frequently in my
> environment. I
> >saw this virtually every time when piping
> > ls | grep | perl
>
> You've actually tried every snapshot from 5/24 and 6/15?
> Wow. I can't
> duplicate this problem, FWIW. It works fine for me.
>
> >Could these two bugs be related? It seems that when the
> terminal emulation
> >bug went away, simultaneously the
> bug appeared.
>
> Probably not.
>
> -chris
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-06-30 22:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 15:57 John Wiersba [this message]
1999-06-30 22:10 ` John Wiersba
-- strict thread matches above, loose matches on Subject: below --
1999-06-24 12:03 John Wiersba
1999-06-24 12:11 ` Chris Faylor
1999-06-30 22:10 ` Chris Faylor
1999-06-30 22:10 ` John Wiersba
1999-06-24 10:56 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-24 10:00 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-24 9:37 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-24 8:18 John Wiersba
1999-06-24 8:29 ` Dr. Volker Zell
1999-06-30 22:10 ` Dr. Volker Zell
1999-06-24 11:51 ` Chris Faylor
1999-06-30 22:10 ` Chris Faylor
1999-06-30 22:10 ` John Wiersba
1999-06-23 15:47 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-23 14:52 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-23 12:42 John Wiersba
1999-06-24 0:49 ` Dr. Volker Zell
1999-06-30 22:10 ` Dr. Volker Zell
1999-06-30 22:10 ` John Wiersba
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=03F4742D8225D21191EF00805FE62B990205E180@AA-MSG-01 \
--to=john.wiersba@medstat.com \
--cc=cygwin@sourceware.cygnus.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).