From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: calm now runs on-demand
Date: Tue, 18 Apr 2017 11:05:00 -0000 [thread overview]
Message-ID: <20170418110549.GE30642@calimero.vinschen.de> (raw)
In-Reply-To: <a2d4b3d6-b7a9-8be4-f17c-d2fd94d3df9d@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Apr 17 12:34, Jon Turney wrote:
>
> I recently deployed an update to calm which should causes it to run
> on-demand after a maintainer SFTP upload.
>
> Hopefully this reduces the inconvenience of having to wait till the next
> scheduled run, after an upload is made which fails due to some easily
> correctable problem.
>
> calm continues to also run on a schedule at :10 and :40 past the hour, so it
> will still note changes which have been made directly on sourceware.
>
> If you have shell access on sourceware, and make such changes, you can force
> calm to run with '~cygwin-admin/bin/calm scan-(uploads|relarea)'.
>
> Given that, it probably makes sense to consider reducing the frequency of
> scheduled runs.
👍
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-04-18 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 11:34 Jon Turney
2017-04-18 11:05 ` Corinna Vinschen [this message]
2017-07-01 11:31 ` Andrew Schulman
2017-07-01 14:04 ` Jon Turney
2017-07-03 16:05 ` Andrew Schulman
2017-07-01 5:18 ` Marco Atzeri
2017-07-01 13:54 ` Jon Turney
2017-07-01 14:14 ` Marco Atzeri
2017-07-01 14:22 ` Jon Turney
2024-04-01 22:46 ` Jon Turney
2017-07-01 14:00 ` Achim Gratz
2017-07-01 14:03 ` Achim Gratz
2017-07-01 14:16 ` 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=20170418110549.GE30642@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).