From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] devproc: Fix a double-free
Date: Fri, 17 Feb 2023 12:42:37 +0100 [thread overview]
Message-ID: <16FCABC39CE6B45389A415387DA69CA6@felloff.net> (raw)
In-Reply-To: <Y+7n3Ei7HUSI/N3g@quark.home.arpa>
good catch!
applied.
thank you very much.
--
cinap
prev parent reply other threads:[~2023-02-17 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 20:35 Josiah Frentsos
2023-02-17 2:35 ` Josiah Frentsos
2023-02-17 11:42 ` cinap_lenrek [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=16FCABC39CE6B45389A415387DA69CA6@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).