public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: calm does not recognize gambas3 3.10.0
Date: Mon, 14 Aug 2017 01:54:00 -0000	[thread overview]
Message-ID: <e917f7a3-8d37-6083-39f4-ca035dbb16da@cornell.edu> (raw)
In-Reply-To: <c3c9dee7-8b63-7f23-42ff-0ac119c9e89e@fishpost.de>

On 8/13/2017 5:12 PM, Bastian Germann wrote:
> Hi,
> 
> I uploaded a new version of gambas3 two days ago, but although the
> !ready file is in place, calm does not care about the files. I do not
> get any error emails to the address in !mail. What is the problem?

Did you create two !ready files, one under x86 and one under x86_64?

Ken

  reply	other threads:[~2017-08-14  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 21:13 Bastian Germann
2017-08-14  1:54 ` Ken Brown [this message]
2017-08-14  7:35 ` Achim Gratz
2017-08-14 16:47 ` Jon Turney
2017-08-14 17:27   ` Achim Gratz

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=e917f7a3-8d37-6083-39f4-ca035dbb16da@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).