From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [[PATCH setup] 0/3] Prepare for colons in version numbers
Date: Mon, 30 Oct 2017 15:55:00 -0000 [thread overview]
Message-ID: <dc25313f-8844-8a02-bb3f-b14915961e00@dronecode.org.uk> (raw)
In-Reply-To: <20171027184723.9324-1-kbrown@cornell.edu>
On 27/10/2017 19:47, Ken Brown wrote:
> A future version of setup might allow version numbers of the form
> e:v-r, where is an epoch. Currently setup doesn't parse these
> correctly when reading installed.db. In case ScanFindVisitor is used,
> there is an additional problem in reading filenames containing colons.
> The reading is done by Win32 functions, and the illegal characters
> like ':' aren't translated.
>
> Ken Brown (3):
> Remove the function filemanip.cc:base
> Bump the installed.db version to 4
> Remove the ScanFindVisitor class
Great, thanks.
I'll hold 2/3 back a bit, as bumping the installed.db version makes it a
pain to go back to the released setup version after testing...
prev parent reply other threads:[~2017-10-30 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 18:47 Ken Brown
2017-10-27 18:47 ` [[PATCH setup] 1/3] Remove the function filemanip.cc:base Ken Brown
2017-10-27 18:47 ` [[PATCH setup] 2/3] Bump the installed.db version to 4 Ken Brown
2017-10-27 18:47 ` [[PATCH setup] 3/3] Remove the ScanFindVisitor class Ken Brown
2017-10-27 19:27 ` [[PATCH setup] 0/3] Prepare for colons in version numbers Achim Gratz
2017-10-27 19:33 ` Ken Brown
2017-10-27 19:48 ` Brian Inglis
2017-10-27 20:31 ` Yaakov Selkowitz
2017-10-30 15:58 ` Jon Turney
2017-10-31 10:06 ` Achim Gratz
2017-10-31 11:21 ` Corinna Vinschen
2017-10-31 16:22 ` Brian Inglis
2017-10-31 18:16 ` Achim Gratz
2017-10-31 18:32 ` Brian Inglis
2017-10-30 15:55 ` Jon Turney [this message]
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=dc25313f-8844-8a02-bb3f-b14915961e00@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).