From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup] Sort the packages listed in the "confirm" dialog
Date: Thu, 07 Jun 2018 17:14:00 -0000 [thread overview]
Message-ID: <c75c4105-6e50-165e-ea73-65e87f827afc@cornell.edu> (raw)
In-Reply-To: <f0cce594-1287-76bf-f4bd-9f52042e8f33@dronecode.org.uk>
On 6/6/2018 4:44 PM, Jon Turney wrote:
> I know you had a few other patchsets in flight, which I've unfortunately
> taken my eye off. If it's easier, you could push a branch with
> somewhere with what's outstanding, and I'll see if I can pick them up.
Here are the patchsets that I've sent in the last few months:
1. https://sourceware.org/ml/cygwin-apps/2018-03/msg00033.html
This still applies to the current HEAD.
2. https://sourceware.org/ml/cygwin-apps/2018-03/msg00051.html
This also applies to the current HEAD.
3. https://sourceware.org/ml/cygwin-apps/2018-04/msg00002.html
This needs to be tweaked slightly. I'll send a v2 today or tomorrow.
Next, there's the tentative proposal I made in
https://sourceware.org/ml/cygwin-apps/2018-04/msg00000.html, with a
cygport patch that isn't quite right. That could use some followup
eventually.
Finally, there's the older patchset attempting to distinguish between
user URLs and Cygwin mirrors:
https://sourceware.org/ml/cygwin-apps/2017-12/msg00051.html
with a followup patchset here:
https://sourceware.org/ml/cygwin-apps/2017-12/msg00066.html
I'm honestly not sure whether this "user URL" idea is worth pursuing,
because it might end up confusing users more than it helps them. But if
you think it is, I'll push it to a branch for further work.
Ken
next prev parent reply other threads:[~2018-06-07 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 16:31 Ken Brown
2018-06-06 20:44 ` Jon Turney
2018-06-07 17:14 ` Ken Brown [this message]
2018-07-09 18:49 ` 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=c75c4105-6e50-165e-ea73-65e87f827afc@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).