From: Vince Rice <vrice@solidrocksystems.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup.ini has multiple "prev" entries ... Why?
Date: Sun, 05 Nov 2017 14:03:00 -0000 [thread overview]
Message-ID: <0ED4C99C-0A72-4F9F-8A2F-4FA2C1EFE039@solidrocksystems.com> (raw)
In-Reply-To: <20e5f0520f9831ecd59e509dc7f7d852@xs4all.nl>
> On Nov 5, 2017, at 6:48 AM, Houder wrote:
>
> Hi John (Turney),
>
> After I had downloaded and exercised setup version 2.882, I noticed
> that setup.ini has multiple (2?) "prev" entries per package ...
>
> Why? Did I miss one of your announcements mentioning this change?
>
> Regards,
>
> Henri
>
> Announcements (setup):
>
> - https://cygwin.com/ml/cygwin/2017-05/msg00313.html -- 2.879
> - https://cygwin.com/ml/cygwin/2017-06/msg00166.html -- 2.880
> - https://cygwin.com/ml/cygwin/2017-07/msg00072.html -- 2.881
> - https://cygwin.com/ml/cygwin/2017-10/msg00285.html -- 2.882
>
> Description (specification?) of setup.ini:
>
> - https://sourceware.org/cygwin-apps/setup.ini.html
It's Jon, and yes, you did. I'm on the way out the door, but you can search the archives. The discussion was on apps, IIRC, and was in the last month or two.
Not Jon
--
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:[~2017-11-05 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 12:48 Houder
2017-11-05 14:03 ` Vince Rice [this message]
2017-11-05 14:20 ` Houder
2017-11-05 14:37 ` Houder
2017-11-05 17:32 ` Houder
2017-11-05 18:04 ` Houder
2017-11-06 14:21 ` Jon Turney
2017-11-06 15:35 ` Houder
2017-11-06 17:37 ` Jon Turney
2017-11-06 16:34 ` Houder
2017-11-06 17:37 ` Jon Turney
2017-11-06 14:20 ` Jon Turney
2017-11-06 16:15 ` Houder
2017-11-06 18:02 ` Achim Gratz
2017-11-07 10:25 ` Houder
2017-11-07 14:19 ` Jon Turney
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=0ED4C99C-0A72-4F9F-8A2F-4FA2C1EFE039@solidrocksystems.com \
--to=vrice@solidrocksystems.com \
--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).