From: "Dave Arnold" <avr_fan@nettaxi.com>
To: "Chris Faylor" <cgf@cygnus.com>, "Jim Ingham" <jingham@apple.com>
Cc: <insight@sourceware.cygnus.com>
Subject: Re: Insight Actually work or is it just an alpha orpre-alpha?
Date: Thu, 06 Jul 2000 02:16:00 -0000 [thread overview]
Message-ID: <000401bfe72c$0d06f400$a6bf1004@homepc.freedsl.com> (raw)
hi,
What is Cygwin b20.1, I always see mention of this but the naming convention
throws me off some reason because people usually leave off the Cygwin, so
they
just refer to it as b20.1. Can anyone tell from this output below if I am
using b20.1?
uname -a gave this;
CYGWIN_95-4.0 HOMEPC 1.1.2(0.21/3/2) 2000-06-06 22:20 i586 unknown
/dave
-----Original Message-----
From: Chris Faylor <cgf@cygnus.com>
To: Jim Ingham <jingham@apple.com>
Cc: Dave Arnold <avr_fan@mailandnews.com>; Dave Arnold
<avr_fan@nettaxi.com>; insight@sourceware.cygnus.com
<insight@sourceware.cygnus.com>
Date: Wednesday, July 05, 2000 6:50 PM
Subject: Re: Insight Actually work or is it just an alpha orpre-alpha?
>On Wed, Jul 05, 2000 at 06:47:50PM -0700, Jim Ingham wrote:
>>Also sprach Dave Arnold:
>>>how do I figure out the cygwin version. I was looking in the cygcheck
>>>output but didn't see it. is there another way?
>>
>>Yeah, there is, but I forget what it is... I am not a big cygwin
>>expert, I just used it a little bit.
>
>'uname -a' will give you the cygwin version. Newer versions of cygcheck
will too.
>
>cgf
next reply other threads:[~2000-07-06 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 2:16 Dave Arnold [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-05 18:41 Dave Arnold
2000-07-05 18:47 ` Jim Ingham
2000-07-05 18:51 ` Chris Faylor
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='000401bfe72c$0d06f400$a6bf1004@homepc.freedsl.com' \
--to=avr_fan@nettaxi.com \
--cc=cgf@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@apple.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).