From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: How to avoid tying up scallywag
Date: Sun, 19 Mar 2023 19:04:10 -0400 [thread overview]
Message-ID: <8ffc47a4-1004-002b-c81f-6cafa7076f95@cornell.edu> (raw)
Jon,
I'll be ready to go with TeX Live 2023 in a couple days. That involves
about 60 packages. If I push them all at once, I'm afraid that would
tie up scallywag and make it unusable by others. I was thinking of
pushing them in batches of 5, with a couple hours in between batches.
But I don't know how many jobs scallywag can do at once. What do you think?
Ken
next reply other threads:[~2023-03-19 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 23:04 Ken Brown [this message]
2023-03-20 3:48 ` marco atzeri
2023-03-20 11:22 ` Jon Turney
2023-03-20 13:14 ` Ken Brown
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=8ffc47a4-1004-002b-c81f-6cafa7076f95@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).