From: Kristo <kristo.ilmari@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] patch your shit
Date: Sun, 25 Aug 2024 06:56:10 +0000 [thread overview]
Message-ID: <861A833C-562E-4697-8FB4-D97F6EB83ED8@gmail.com> (raw)
In-Reply-To: <CAFSF3XO6BLKzBX1RgPYaxPSXF9NgNmTCm3XDWLiF1+KEi__=nQ@mail.gmail.com>
On August 24, 2024 7:08:42 PM UTC, hiro <23hiro@gmail.com> wrote:
>This security bug is still pending a cute mascot and theme song.
Don't forget the CVE identifier.
next prev parent reply other threads:[~2024-08-25 6:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 19:08 hiro
2024-08-24 20:15 ` Willow Liquorice
2024-08-24 21:21 ` Jacob Moody
2024-08-24 21:25 ` adventures in9
2024-08-24 21:37 ` sl
2024-08-24 21:40 ` Willow Liquorice
2024-08-24 21:55 ` Eli Cohen
2024-08-24 22:18 ` Jacob Moody
2024-08-25 0:55 ` Jacob Moody
2024-08-25 10:27 ` rgl
2024-08-25 6:56 ` Kristo [this message]
2024-08-26 14:32 ` hiro
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=861A833C-562E-4697-8FB4-D97F6EB83ED8@gmail.com \
--to=kristo.ilmari@gmail.com \
--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).