From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Jari Aalto <jari.aalto@cante.net>, Chad Dougherty <crd@acm.org>
Subject: Re: [ITP] rsync 3.2.6
Date: Fri, 2 Dec 2022 15:07:23 +0000 [thread overview]
Message-ID: <deff6bfd-17e5-1d66-17bd-5537449f953e@dronecode.org.uk> (raw)
In-Reply-To: <c9f62b84-f1bf-e14a-5837-1c42364e5dd3@dronecode.org.uk>
On 09/10/2022 15:23, Jon Turney wrote:
> On 06/10/2022 02:29, Chad Dougherty wrote:
>> Hello all,
>>
>> I've been using cygwin for a long time but this is my first attempt at
>> this process so please be gentle :)
>>
>> I noticed that the current rsync package (3.2.3+20200903+git9f9240b-4)
>> is trailing on security updates and also still using the g-b-s method.
>> I pinged the listed maintainer directly last week asking if they were
>> planning to do any updates but have not heard back. I hope this was
>> not a faux pas as I didn't read until later that it's best to raise
>> the issue on the list first.
>>
>> I've attempted to update the port here:
>> https://github.com/crd477/cygports/tree/main/rsync
>>
> [...]
>> This package also seemed to work OK with some casual real testing.
>>
>
> Thanks for looking into updating this. I'd like to give the existing
> maintainer first refusal, though.
No response from Jari, 8 weeks have elapsed, so I've given
maintainership to Chad.
Jari,
Hope you are ok. Please let me know if this isn't what you wanted.
prev parent reply other threads:[~2022-12-02 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 1:29 Chad Dougherty
2022-10-06 17:24 ` Adam Dinwoodie
2022-10-06 18:20 ` Chad Dougherty
2022-10-06 20:01 ` Ken Brown
2022-10-09 14:23 ` Jon Turney
2022-10-09 21:18 ` Brian Inglis
2022-10-10 0:28 ` Chad Dougherty
2022-10-10 7:15 ` ASSI
2022-10-26 0:44 ` Chad Dougherty
2022-12-02 15:07 ` Jon Turney [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=deff6bfd-17e5-1d66-17bd-5537449f953e@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=crd@acm.org \
--cc=cygwin-apps@cygwin.com \
--cc=jari.aalto@cante.net \
/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).