From: gentoo_bugs_peep@parallaxshift.com
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] help
Date: Tue, 9 Jan 2024 12:45:00 -0500 [thread overview]
Message-ID: <4e07df1b-05e2-4764-a5ba-203c736fea9a@parallaxshift.com> (raw)
help
next reply other threads:[~2024-01-09 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 17:45 gentoo_bugs_peep [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 21:09 [gentoo-dev] help darveter
2014-03-01 15:18 slepnoga
2006-06-27 15:18 Dan Podeanu
2006-06-27 21:14 ` Michael Cummings
2006-06-27 23:02 ` Raphael Marichez
2001-04-06 8:06 [gentoo-dev] Help Bryce Porter
2001-04-06 8:28 ` Daniel Robbins
2001-04-06 8:39 ` Jerry A!
2001-04-06 8:41 ` Daniel Robbins
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=4e07df1b-05e2-4764-a5ba-203c736fea9a@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