From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Installer names not meaningful enough
Date: Mon, 05 Dec 2016 18:53:00 -0000 [thread overview]
Message-ID: <2a8450b4-667b-decb-3af3-5e9a2849d6ad@cs.umass.edu> (raw)
In-Reply-To: <1921963768.20161205212541@yandex.ru>
On 12/5/2016 1:25 PM, Andrey Repin wrote:
> Greetings, Stephen Paul Carrier!
>
>> I don't mind renaming the file myself, but would really appreciate any
>> way to know from the cygwin.com front page exactly which version of the
>> setup-*.exe is on offer. (The current version of Cygwin DLL is useful,
>> but not the same thing.)
>
> That may (will!) confuse people not familiar with insides of Cygwin
> environment.
Possibly, but it doesn't strike me as overly difficult to explain
that these are different version sequences. We also might be able
to make the two numbering schemes look sufficiently different that
they would be harder to confuse ...
Regards - Eliot Moss
--
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:[~2016-12-05 18:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 10:52 Roberto Ríos Gallardo
2016-12-01 12:19 ` Lee Dilkie
2016-12-01 12:51 ` Eliot Moss
2016-12-01 13:25 ` Vlado
2016-12-01 13:55 ` cyg Simple
2016-12-01 16:37 ` Ian Lambert
2016-12-05 17:36 ` Stephen Paul Carrier
2016-12-05 18:35 ` Andrey Repin
2016-12-05 18:53 ` Eliot Moss [this message]
2016-12-05 19:05 ` Brian Inglis
2016-12-01 14:06 ` Buchbinder, Barry (NIH/NIAID) [E]
2016-12-07 21:40 ` Erik Soderquist
2016-12-07 21:57 ` Brian Inglis
2016-12-07 22:06 ` Erik Soderquist
2016-12-08 4:50 ` Brian Inglis
2016-12-09 11:28 ` Vlado
2016-12-14 21:18 ` Erik Soderquist
2016-12-14 21:50 ` cyg Simple
2016-12-14 21:58 ` Erik Soderquist
2016-12-15 15:54 ` cyg Simple
2016-12-06 9:12 ` Gerrit Haase
2016-12-07 9:57 ` Duncan Roe
2016-12-07 14:46 ` Ian Lambert
2016-12-07 21:25 ` Brian Inglis
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=2a8450b4-667b-decb-3af3-5e9a2849d6ad@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).