From: Chad Dougherty <crd@acm.org>
To: Adam Dinwoodie <adam@dinwoodie.org>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] lz4
Date: Sun, 23 Oct 2022 20:39:45 -0400 [thread overview]
Message-ID: <5efaf04b-5030-0ea2-2763-8bd0bb773255@acm.org> (raw)
In-Reply-To: <CA+kUOak4LLzWBMN6t+HtLMEJznVXRcq_VB-ZUHEWxMQwdTdKew@mail.gmail.com>
On 2022-10-23 13:31, Adam Dinwoodie wrote:
> On Sat, 22 Oct 2022 at 21:59, Chad Dougherty wrote:
>> I'd like to adopt the lz4 library that is currently listed as orphaned.
>>
>> I've updated the cygport to the current version, 1.9.4:
>> https://github.com/crd477/lz4-cygport
>
> I've not tested the actual compilation, but I have done some test
> builds, and this all looks good to me!
>
Great!
>> Is it acceptable for me to put these updates into the cygwin git repository?
>
> Once you're listed as a maintainer, yes; up until then, you won't have
> permission to write to that repository.
>
I see. I didn't appreciate that maintainership was also factored into
the authorization process but it makes sense. Jon mentioned this in the
passwdqc thread as well.
>> Also, is it expected that I should also take the
>> mingw64-{i686,x86_64}-lz4 packages too?
>
> AIUI that's preferred but not required; they're separate packages, so
> it's entirely possible for them to have separate maintainers.
OK, I updated them here:
https://github.com/crd477/mingw64-x86_64-lz4-cygport
https://github.com/crd477/mingw64-i686-lz4-cygport
I've had less experience with cross-compiling but I think they're
correct nevertheless.
Thanks, and take care...
--
-Chad
next prev parent reply other threads:[~2022-10-24 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 20:59 Chad Dougherty
2022-10-23 17:31 ` Adam Dinwoodie
2022-10-24 0:39 ` Chad Dougherty [this message]
2022-10-30 14:26 ` Jon Turney
2022-10-30 16:55 ` Chad Dougherty
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=5efaf04b-5030-0ea2-2763-8bd0bb773255@acm.org \
--to=crd@acm.org \
--cc=adam@dinwoodie.org \
--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).