From: Jon Turney <jon.turney@dronecode.org.uk>
To: Thomas Wolff <towo@towo.net>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Cygwin x86 end-of-life
Date: Sat, 12 Nov 2022 16:08:55 +0000 [thread overview]
Message-ID: <96fd446b-5c5f-6304-9eda-c007cb33196e@dronecode.org.uk> (raw)
In-Reply-To: <df5e08f5-1777-52a9-f2b8-b89b708a545d@towo.net>
On 11/11/2022 20:02, Thomas Wolff wrote:
> Hi Achim,
>
> Am 11.11.2022 um 20:50 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>>> I plan to pause package uploads this coming Monday (2022-11-14),
>>>> before starting the re-organization of the package repository to
>>>> make this archive.
>>> Although expected for a while, the exact date is now a very short-time
>>> announcement. Can we have a moratorium for a short while?
So, if not now, when?
Is this actually going to cause you problems, and if so what are they
specifically, or is this just a case of "change is bad"?
>> That moratorium is already running for more than a year:
>>
>> https://cygwin.com/pipermail/cygwin/2021-October/249690.html
> That message does not announce a blocking of further 32-bit package
> uploads, and not a precise date for such hard step either. So please
> let's not commit a violation of the principle of least surprise.
Sorry if this was communicated in a surprising way, but there is also
another, important principle at work here, the principle of least
effort, or as we might call it in this application "the principle of not
inventing more work for Jon Turney to do".
next prev parent reply other threads:[~2022-11-12 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cfc30991-0dd0-3308-9aca-df7cf81169aa@dronecode.org.uk>
2022-11-11 16:16 ` Jon Turney
2022-11-11 19:45 ` Thomas Wolff
2022-11-11 19:50 ` Achim Gratz
2022-11-11 20:02 ` Thomas Wolff
2022-11-12 16:08 ` Jon Turney [this message]
2022-11-12 16:58 ` Thomas Wolff
2022-11-13 13:58 ` Thomas Wolff
2022-11-13 16:43 ` Achim Gratz
2022-11-13 17:01 ` Thomas Wolff
2022-11-13 17:07 ` Jon Turney
2022-11-13 19:17 ` Corinna Vinschen
2022-11-14 15:24 ` Andrew Schulman
2022-11-13 20:31 ` Brian Inglis
2022-11-14 16:25 ` Jon Turney
2022-11-14 17:18 ` Andrew Schulman
2022-11-14 20:16 ` Brian Inglis
2022-11-14 21:29 ` Jason Pyeron
2022-11-18 15:51 ` Jon Turney
2022-11-15 19:14 ` Erwin Waterlander
2022-11-28 13:08 ` Jon Turney
2022-11-21 12:45 Corinna Vinschen
2022-11-22 17:51 ` Brian Inglis
2022-11-22 21:07 ` Achim Gratz
2022-11-23 20:00 ` Brian Inglis
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=96fd446b-5c5f-6304-9eda-c007cb33196e@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=towo@towo.net \
/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).