From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18252 invoked by alias); 1 Jul 2017 11:31:46 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 18139 invoked by uid 89); 1 Jul 2017 11:31:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*r:Unknown, sftp, SFTP, H*Ad:D*gov X-HELO: blaine.gmane.org Received: from Unknown (HELO blaine.gmane.org) (195.159.176.226) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 01 Jul 2017 11:31:43 +0000 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dRGcg-0007f2-RP for cygwin-apps@cygwin.com; Sat, 01 Jul 2017 13:31:34 +0200 To: cygwin-apps@cygwin.com From: Andrew Schulman Subject: Re: calm now runs on-demand Date: Sat, 01 Jul 2017 11:31:00 -0000 Message-ID: References: <20170418110549.GE30642@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes X-SW-Source: 2017-07/txt/msg00006.txt.bz2 > 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. I have upload access, but AFAIK not shell access. I think most maintainers don't, unless that's changed.