From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: mintty should have skipped one version
Date: Sun, 07 Oct 2018 03:53:00 -0000 [thread overview]
Message-ID: <3cb57895-9fdd-0007-f7bd-a8932439b7aa@SystematicSw.ab.ca> (raw)
In-Reply-To: <efd59481-6eb1-f42e-cfc9-157947660b46@towo.net>
On 2018-10-06 21:32, Thomas Wolff wrote:
> I think I uploaded mintty 2.9.3 with a dedicated mintty-2.9.3-0.hint file with
> the first two lines
> curr: 2.9.3-0
> prev: 2.9.1-0
> but setup still offers 2.9.2 as a choice. Did I miss the point in the upload
> procedure?
Maybe use override.hint instead as described in:
https://cygwin.com/ml/cygwin-apps/2018-08/msg00047.html
where replace-versions should reference 2.9.2-?, and should the releases all be
...-0 rather than the standard ...-1?
--
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.
next prev parent reply other threads:[~2018-10-07 3:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 3:32 Thomas Wolff
2018-10-07 3:53 ` Brian Inglis [this message]
2018-10-07 9:19 ` Thomas Wolff
2018-10-07 9:23 ` Marco Atzeri
2018-10-07 9:31 ` Achim Gratz
2018-10-07 9:04 ` Marco Atzeri
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=3cb57895-9fdd-0007-f7bd-a8932439b7aa@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@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).