From: Ivan Gagis <igagis@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: mksetupini fails validating packages because curr is test
Date: Mon, 04 Dec 2017 12:02:00 -0000 [thread overview]
Message-ID: <CAL_02JDb_eq1PC4fbWif5rr_MzfOa+r_6E25XGvK3Z5SNHb1LA@mail.gmail.com> (raw)
In-Reply-To: <ce8713b5-48bf-3792-6353-2fa77dcb8b45@dronecode.org.uk>
Ok, thanks! But what would be the schedule of releasing it to cygwin repo?
I don't want to mess up my CI scripts which install the whole build
env from scratch on every build, so I need it in cygwin repo.
Br,
Ivan
2017-12-01 13:00 GMT+02:00 Jon Turney <jon.turney@dronecode.org.uk>:
> On 30/11/2017 22:16, Ivan Gagis wrote:
>>
>> Thanks for prompt actions!
>
>
> No problem.
>
>> I think no need to package it separately for testing, just release it
>> to cygwin repo.
>
>
> Ok. You can get it with:
>
> pip3 install git+http://cygwin.com/git/cygwin-apps/calm.git
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-12-04 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 15:07 Ivan Gagis
2017-11-29 16:52 ` Jon Turney
[not found] ` <CAL_02JC8t9TM6bRyrovCVJRv+pogdn+fNH7kv8ha016XZw0irA@mail.gmail.com>
2017-11-29 22:13 ` Jon Turney
2017-11-30 9:29 ` Ivan Gagis
2017-11-30 12:41 ` Jon Turney
2017-11-30 22:16 ` Ivan Gagis
2017-12-01 11:00 ` Jon Turney
2017-12-04 12:02 ` Ivan Gagis [this message]
2017-12-04 14:00 ` Jon Turney
2017-12-04 16:57 ` Ivan Gagis
2017-11-30 18:11 ` Wayne Davison
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=CAL_02JDb_eq1PC4fbWif5rr_MzfOa+r_6E25XGvK3Z5SNHb1LA@mail.gmail.com \
--to=igagis@gmail.com \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).