public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ian Lambert via cygwin" <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: RE: How to find out the current cygwin version?
Date: Fri, 08 Sep 2017 15:39:00 -0000	[thread overview]
Message-ID: <1887FC94-CBF3-46D2-A11D-B036DD3741AD@yahoo.com> (raw)
In-Reply-To: <BN6PR2001MB10744EF61D075A11B74EE258F1950@BN6PR2001MB1074.namprd20.prod.outlook.com>

On September 8, 2017 9:05:31 AM EDT, "Nellis, Kenneth" <Kenneth.Nellis@conduent.com> wrote:
>From: David Billinghurst 
>> On 8/09/2017 14:39, Ben Stover via cygwin wrote:
>> 
>> > Assume I get to another (Windows) computer where Cygwin is already
>> installed.
>> >
>> > How can I find out which version of Cygwin is currently installed?
>> cygcheck --version             # for cygwin dll
>> ...
>
>This isn't technically correct, right? This gives the version of
>cygcheck itself, not the cygwin DLL, which is what was really
>being requested.
>
>Instead, use: cygcheck -c cygwin
>
>Or, as I do (and Corinna already suggested): uname -a
>or, more quietly: uname -r
>

Fwiw, from what I've seen, only 
cygcheck -c cygwin 
gives the full x.y.z-n version.
All other suggestions give only
x.y.z without -n

Small difference, but...




-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

.

--
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

  reply	other threads:[~2017-09-08 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08  4:40 Ben Stover via cygwin
2017-09-08  4:44 ` David Billinghurst
2017-09-08  8:16   ` Corinna Vinschen
2017-09-08 13:06   ` Nellis, Kenneth
2017-09-08 15:39     ` Ian Lambert via cygwin [this message]
2017-09-08 15:41   ` Larry Hall (Cygwin)

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=1887FC94-CBF3-46D2-A11D-B036DD3741AD@yahoo.com \
    --to=cygwin@cygwin.com \
    --cc=ian.lambert_42@yahoo.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).