From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: setup with experimental libsolv-based dependency solving
Date: Mon, 22 Jan 2018 17:54:00 -0000 [thread overview]
Message-ID: <9f56e8d6-d5c1-1ea7-37f0-6e92e0598864@cornell.edu> (raw)
In-Reply-To: <222e08ca-5ab9-cbf7-7d07-13a8a96c0d0b@dronecode.org.uk>
On 1/18/2018 2:15 PM, Jon Turney wrote:
> On 23/11/2017 18:08, Jon Turney wrote:
> I'm interested in opinion on what else is needed, before this can be
> released as 2.885
I think we're in pretty good shape except for the issue of letting the
user see what's about to be done before we do it. My latest attempt,
sent a few minutes ago, may or may not be good enough.
Ken
prev parent reply other threads:[~2018-01-22 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 19:19 Jon Turney
2017-10-26 5:41 ` Achim Gratz
2017-10-26 12:06 ` Jon Turney
2017-10-26 17:36 ` Achim Gratz
2017-10-27 18:57 ` Ken Brown
2017-10-27 19:52 ` Ken Brown
2017-10-28 12:31 ` Ken Brown
2017-10-29 17:26 ` Jon Turney
2017-10-30 15:52 ` Jon Turney
2017-11-23 18:08 ` Jon Turney
2018-01-18 19:15 ` Jon Turney
2018-01-22 17:54 ` Ken Brown [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=9f56e8d6-d5c1-1ea7-37f0-6e92e0598864@cornell.edu \
--to=kbrown@cornell.edu \
--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).