public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nedko Arnaudov <nedko@nedk.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Maintainer-needed: G15 keyboard stack
Date: Thu, 30 May 2024 19:58:07 +0300	[thread overview]
Message-ID: <87ikyvi6e8.fsf@pubis.nedk.org> (raw)
In-Reply-To: <robbat2-20240529T185323-477923075Z@orbis-terrarum.net> (Robin H. Johnson's message of "Wed, 29 May 2024 18:55:49 +0000")

"Robin H. Johnson" <robbat2@gentoo.org> writes:

> The G15 keyboard stack need a new maintainer.
>
> My last G15-based keyboard died a few months ago, and I cannot test these
> anymore.
>
> Given the poor upstream code quality, I strongly suggest last-rites if nobody
> is found.
>
> app-misc/g15composer
> app-misc/g15daemon
> app-misc/g15macro
> app-misc/g15message
> app-misc/g15stats
> dev-libs/libg15
> dev-libs/libg15render


My G15 is still working (not sure for how long this will be tho).
I can help with testing.


      parent reply	other threads:[~2024-05-30 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 18:55 [gentoo-dev] Maintainer-needed: G15 keyboard stack Robin H. Johnson
2024-05-30 13:25 ` Matt Turner
2024-05-30 16:58 ` Nedko Arnaudov [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=87ikyvi6e8.fsf@pubis.nedk.org \
    --to=nedko@nedk.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=robbat2@gentoo.org \
    /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