From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [PR] cygport (update required for autoconf-2.71)
Date: Sun, 2 Jan 2022 14:00:08 -0500 [thread overview]
Message-ID: <252e466f-c7bb-d95c-069f-880c92cec4cb@cornell.edu> (raw)
In-Reply-To: <ac309db5-0adf-29fb-3276-30c5b3a8cdb3@gmail.com>
On 1/2/2022 12:22 PM, Marco Atzeri wrote:
> On 05.12.2021 10:34, Achim Gratz wrote:
>>
>> In order for cygport to work correctly when autoconf 2.71 is requested,
>> please pull the first commit (b25cb3faa) on my to-upstream branch into
>> upstream and release a new version. I'd appreciate if the full branch
>> would be pulled, these are all used by me for quite some time already.
>>
> ...
>>
>>
>> Regards,
>> Achim.
>
> I see that "officially" Yaakov is still the maintainer
>
> https://cygwin.com/packages/summary/cygport.html
>
> but I do not remember any commitment from him to do so.
>
> If Yaakov declines, how can we manage the ownership ?
There was a discussion on IRC in which Jon Turney agreed to take over.
Ken
prev parent reply other threads:[~2022-01-02 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 9:34 Achim Gratz
2022-01-02 17:22 ` Marco Atzeri
2022-01-02 19:00 ` Ken Brown [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=252e466f-c7bb-d95c-069f-880c92cec4cb@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).