From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wxWidgets3.0
Date: Sun, 22 Nov 2020 10:43:26 +0100 [thread overview]
Message-ID: <877dqdloap.fsf@Rainer.invalid> (raw)
In-Reply-To: <e05bece7-4b53-9e7a-8966-0f137e0e9542@SystematicSw.ab.ca> (Brian Inglis's message of "Sat, 21 Nov 2020 14:56:28 -0700")
Brian Inglis writes:
> Push your cygport to the git-cygwin-packages playground repo (see Jon
> Turney's recent reply to me in this list) which all maintainers can
> push to, as you don't yet own the git-cygwin-packages wxWidgets repo;
> check the CI jobs.cgi log contents, and fix any issues.
Fun fact: that will certainly run into the build timeout that is
currently set at 1 hour. Jon, do you think it'd be possible to have
another SCALLYWAG variable to extend that limit for the packages that
need it?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2020-11-22 9:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 19:20 Hamish McIntyre-Bhatty
2020-10-17 0:21 ` Lemures Lemniscati
2020-10-17 13:17 ` Hamish McIntyre-Bhatty
2020-10-17 15:04 ` Brian Inglis
2020-10-19 15:31 ` Hamish McIntyre-Bhatty
2020-10-21 13:57 ` Hamish McIntyre-Bhatty
2020-10-21 17:17 ` Brian Inglis
2020-10-21 18:39 ` Achim Gratz
2020-10-27 11:53 ` Hamish McIntyre-Bhatty
2020-10-27 13:16 ` ASSI
2020-10-28 2:21 ` Hamish McIntyre-Bhatty
2020-10-28 8:40 ` Achim Gratz
2020-10-30 19:39 ` Hamish McIntyre-Bhatty
2020-11-11 15:15 ` Hamish McIntyre-Bhatty
2020-11-11 17:36 ` Hamish McIntyre-Bhatty
2020-11-12 18:00 ` Hamish McIntyre-Bhatty
2020-11-21 16:52 ` Hamish McIntyre-Bhatty
2020-11-21 21:56 ` Brian Inglis
2020-11-22 9:43 ` Achim Gratz [this message]
2021-01-08 17:07 ` Hamish McIntyre-Bhatty
2021-01-08 17:15 ` Achim Gratz
2020-11-22 9:41 ` Achim Gratz
2020-11-23 12:53 ` Hamish McIntyre-Bhatty
2020-11-23 15:26 ` ASSI
2020-11-23 16:18 ` Hamish McIntyre-Bhatty
2020-11-23 19:16 ` ASSI
2020-11-23 19:24 ` Hamish McIntyre-Bhatty
2020-11-23 19:34 ` Hamish McIntyre-Bhatty
2020-11-23 20:05 ` ASSI
2020-11-23 20:11 ` Hamish McIntyre-Bhatty
2020-11-24 10:15 ` Hamish McIntyre-Bhatty
2020-11-24 10:43 ` Hamish McIntyre-Bhatty
2020-11-24 19:51 ` Hamish McIntyre-Bhatty
2020-11-25 10:02 ` Hamish McIntyre-Bhatty
2020-12-09 20:55 ` Hamish McIntyre-Bhatty
2020-12-13 20:12 ` Marco Atzeri
2020-12-14 9:46 ` Hamish McIntyre-Bhatty
2020-12-14 20:21 ` Marco Atzeri
2020-12-15 1:49 ` Hamish McIntyre-Bhatty
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=877dqdloap.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).