public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Orphaning fzf
Date: Wed, 2 Feb 2022 10:44:30 +0100	[thread overview]
Message-ID: <YfpSfjAje9D11pRa@calimero.vinschen.de> (raw)
In-Reply-To: <20220201212221.2ymlhw7jktoymsws@lucy.dinwoodie.org>

On Feb  1 21:22, Adam Dinwoodie wrote:
> The upstream fzf package moved from Ruby to Go some time ago.  I had
> vague but noble intetions to try to maintain a fork on the basis of the
> last version of the Ruby code, but never managed anything useful.  In
> that context, I expect it's time that I officially throw in the towel,
> and mark fzf as orphaned.
> 
> The existing build still works, and I don't think there's likely to be
> any crass security problems or anything like that.  But there's no
> longer any upstream support, and I clearly don't have the capacity to
> properly maintain it solo.
> 
> I'm not quite sure what the process is here, but I suspect it's just a
> case of someone with the appropriate access making an update to
> https://cygwin.com/cygwin-pkg-maint

Done.


Thanks,
Corinna

  reply	other threads:[~2022-02-02  9:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 21:22 Adam Dinwoodie
2022-02-02  9:44 ` Corinna Vinschen [this message]
2022-02-04  5:27   ` Go or Rust Packages? Brian Inglis
2022-02-04  6:57     ` Marco Atzeri
2022-02-04  9:23       ` Jan Nijtmans
2022-02-04 21:17         ` Marco Atzeri
2022-02-04 21:32       ` ASSI
2022-02-05 21:25         ` Achim Gratz
2022-02-06 11:09           ` Achim Gratz
2022-02-04  8:14     ` Mark Geisert
2022-02-04  9:12       ` Corinna Vinschen

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=YfpSfjAje9D11pRa@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).