From: namgo <namgo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: berry spawn zombie process
Date: Tue, 03 Oct 2023 19:20:51 +0200 [thread overview]
Message-ID: <20231003172051.Lb6D5QsEbY9uEoVNf5mDK8epxU4XER0ex6LGnxvdehk@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: 360 bytes --]
New comment by namgo on void-packages repository
https://github.com/void-linux/void-packages/issues/46039#issuecomment-1745408140
Comment:
Oh! I might be on the wrong track, we can import the patch provided into the repo until the next official release. Are you comfortable doing this? If not I'll be able to work on it once I'm finished with another issue.
next prev parent reply other threads:[~2023-10-03 17:20 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
2023-10-03 16:52 ` Fremen2001
2023-10-03 17:20 ` namgo [this message]
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=20231003172051.Lb6D5QsEbY9uEoVNf5mDK8epxU4XER0ex6LGnxvdehk@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).