From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: About the opam package
Date: Tue, 21 Jul 2020 09:06:59 -0600 [thread overview]
Message-ID: <f2d0b361-4e79-918b-7504-17a948901a83@SystematicSw.ab.ca> (raw)
In-Reply-To: <5176a7c6-7bb2-027d-ed6d-488da7318c43@dronecode.org.uk>
On 2020-07-17 07:08, Jon Turney wrote:
> On 15/07/2020 03:25, Andy Li wrote:
>> On Wed, Jul 15, 2020 at 7:17 AM Sora Morimoto wrote:
>>> Now, I wanted to help with the maintenance of the opam package for
>>> Cygwin, but after reading the documentation I still do not know
>>> what to do. Specifically, I do not even know where the build script
>>> source is, and where to send the patch.
>>
>> I'm the maintainer of the opam cygwin package. (FYI, you can see the
>> list of cygwin package maintainer at
>> https://cygwin.com/cygwin-pkg-maint)
>> The package source is at https://github.com/andyli/opam-cygwin
>> Feel free to send me PR.
> Please consider mirroring that repo to cygwin.com/git/cygwin-packages/ (as
> detailed at [1])
>
> [1] https://cygwin.com/packaging/repos.html
Might want to remind ITA adopters (300 to go) they need to git clone before
cygport-ing and commit before git push-ing - I had a duh! moment before I
realized what's up. ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2020-07-21 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 23:17 Sora Morimoto
2020-07-15 1:43 ` Brian Inglis
2020-07-15 2:56 ` Sora Morimoto
2020-07-15 2:25 ` Andy Li
2020-07-15 2:52 ` Sora Morimoto
2020-07-17 13:08 ` Jon Turney
2020-07-19 8:44 ` Andy Li
2020-07-21 15:06 ` Brian Inglis [this message]
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=f2d0b361-4e79-918b-7504-17a948901a83@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).