From: namgo <namgo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: berry spawn zombie process
Date: Tue, 03 Oct 2023 17:11:03 +0200 [thread overview]
Message-ID: <20231003151103.MSx6j-69tNh5pjy8atVzVUSBejOTz3S25EH8kbhvG48@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46039@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
New comment by namgo on void-packages repository
https://github.com/void-linux/void-packages/issues/46039#issuecomment-1745180941
Comment:
Berry's latest version on github (Oct 2022) predates the patch mentioned (Nov 2022).
I'm somewhat new to package maintenance, is the correct solution to request that the Berry WM maintainer make a new release?
next prev parent reply other threads:[~2023-10-03 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 1:01 [ISSUE] " Fremen2001
2023-10-03 15:11 ` namgo [this message]
2023-10-03 16:52 ` Fremen2001
2023-10-03 17:20 ` namgo
2023-10-04 12:47 ` [ISSUE] [CLOSED] " abenson
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=20231003151103.MSx6j-69tNh5pjy8atVzVUSBejOTz3S25EH8kbhvG48@z \
--to=namgo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).