X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9575538618B8
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=SystematicSw.ab.ca
Authentication-Results: sourceware.org;
 spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis: v=2.3 cv=LKf9vKe9 c=1 sm=1 tr=0
 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=McOlyyESAAAA:8 a=Ed7FdIT4gc43trk-okQA:9
 a=mJ7bB_j6NIQQ1T1n:21 a=8D5xw-7GD-MBbF4m:21 a=QEXdDO2ut3YA:10
 a=9c8rtzwoRDUA:10 a=sRI3_1zDfAgwuvI8zelB:22 a=UoH3Eknu7Sz4exW7_WxQ:22
Subject: Re: FAQ 1.5 changes (was: How to check cygwin version?)
To: cygwin AT cygwin DOT com
References: <CAH8yC8noPqzyKHyNVhfnsPB5umhMj0wDiAvz1Jur_7s9LCe7xg AT mail DOT gmail DOT com>
 <f6c689bd-d40a-de0f-5c46-14053f0b1eef AT SystematicSw DOT ab DOT ca>
 <0c35113f-7b72-56d0-a032-b0cfa045f7ee AT huarp DOT harvard DOT edu>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Autocrypt: addr=Brian DOT Inglis AT SystematicSw DOT ab DOT ca; prefer-encrypt=mutual;
 keydata=
 mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0
 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA
 PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW
 AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO
 WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB
 BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5
 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF
 IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5
 RSyTY8X+AQ==
Organization: Systematic Software
Message-ID: <4b5a8c04-ae4f-6e2b-e22d-8e960dd305b7@SystematicSw.ab.ca>
Date: Thu, 2 Jul 2020 21:38:42 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <0c35113f-7b72-56d0-a032-b0cfa045f7ee@huarp.harvard.edu>
Content-Language: en-CA
X-CMAE-Envelope: MS4wfN9QtFpfkvua3NiL/VTaa3j0aP51Vp8k5hVa8STe0I4iOFMxfs9tWDjcSdgkmNvAUEf5GBf7X9x29xtaAFjpL9GHGs7X8F1Wl22mwOJ5MTvV+6y8VdBy
 EYodRQtAD2rHtV0kYTycDd90YNN1tC0WTM05wZA88pVcOgHLuzVIHn6agGVsII3PuwkgGcHJP4kThA==
X-Spam-Status: No, score=-8.3 required=5.0 tests=BAYES_00, BODY_8BITS,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <http://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 0633dFXp027152

On 2020-07-02 09:34, Norton Allen wrote:
> On 7/2/2020 1:20 AM, Brian Inglis wrote:
>> On 2020-07-01 07:36, Jeffrey Walton via Cygwin wrote:
>>> I think the documentation leaves a lot to be desired... I'm trying to
>>> tell someone what version of Cygwin I am using.
>>> There's a FAQ item at
>>> https://cygwin.com/faq/faq.html#faq.what.version. It gives this
>>> useless advice:
>>>     To find the version of the Cygwin DLL installed, you can use uname
>>>     as on Linux or cygcheck. Refer to each command's --help output and
>>>     the Cygwin User's Guide for more information.
>>> OK, let's try it:
>>> $ cygcheck -v
>>> Usage: cygcheck [-v] [-h] PROGRAM
>>>         cygcheck -c [-d] [PACKAGE]
>>>         cygcheck -s [-r] [-v] [-h]
>>>         cygcheck -k
>>>         ...
>>> OK, -v is what we need:
>>> $ cygcheck -v cygwin
>>> cygcheck: could not find 'cygwin'
>>> OK, another failure.
>>> RTFM does not work. Why the hell don't you just state how to check the
>>> god damn version?

>> Do you think it would help if this FAQ entry were changed to read:
>>
>> 1.5. What version of Cygwin is this, anyway?
>>       To find the version of the Cygwin DLL installed, you can use any of the
>> Cygwin commands uname -a, uname -srvm, head /proc/version as on Linux, or
>> cygcheck -V. Refer to each command's --help output or the Cygwin User's Guide
>> for more information.
>>
>> and please make any further comments, feedback, or suggestions you think would
>> help with this entry.

> I think what is missing in all these suggestions is a clear statement that for
> Cygwin's purposes, the cygwin DLL is considered to be the 'kernel', so looking
> for the 'kernel release' gives you the DLL version. I think that leap is totally
> non-obvious.

Okay folks, would this approach make the situation and operations clearer:

1.5. What version of Cygwin is this, anyway?

As the Cygwin DLL takes the place of a Unix kernel, to find the version of the
Cygwin DLL installed, you can use any of the Unix compatible commands: uname -a;
uname -srvm; head /proc/version; or the Cygwin command: cygcheck -V. Refer to
each command's --help output or the Cygwin User's Guide for more information.

and again please feel free to make any further comments, feedback, or
suggestions you think would help with this entry.

[I intend to submit a patch to cygwin-patches at cygwin.com to change lines
56-60 of https://cygwin.org/git/?p=cygwin-htdocs.git;a=blob;f=faq/faq.html

Anyone with a similar interest or annoyance at any of the FAQ entries may do so:
git clone the rep;
edit the minimal number of files and lines required to make your change;
git diff to check the impact of your changes;
git stage/add the file/s changed;
git commit the change using option -F <file> with a short first message line to
be used as email subject with more details in normal length following lines or
-m '...' multiline comment;
git format-patch -1;
git send-email 0001-...patch to the patches email address.
One of the volunteer committers will eventually notice and apply the patch, or
provide feedback about what and why changes will be required to apply the patch.]

-- 
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.
[Data in IEC units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple