From: gentoo_bugs_peep@parallaxshift.com
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: help
Date: Wed, 10 Jan 2024 08:26:25 -0500 [thread overview]
Message-ID: <4a2b9d99-b7c8-4b4f-9feb-13241c489682@parallaxshift.com> (raw)
On 1/10/2024 6:51 AM, Sam James wrote:
>
> gentoo_bugs_peep@parallaxshift.com writes:
>
>> help
>
> ???
Whoops! Sorry about that. I brain farted and thought this was a
mailinglist control e-mail address. And I'm on the digest, so I hadn't
received my own stupidity sent back to myself yet. Only realized when
Sam pinged me.
Should have just done a websearch to end up at
https://www.gentoo.org/get-involved/mailing-lists/instructions.html
Again. Apologies for the spam.
reply other threads:[~2024-01-10 13:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4a2b9d99-b7c8-4b4f-9feb-13241c489682@parallaxshift.com \
--to=gentoo_bugs_peep@parallaxshift.com \
--cc=gentoo-dev@lists.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