From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] is the appropriate forum to ask about the uclibc stages?
Date: Wed, 20 Apr 2005 11:03:57 -0400 [thread overview]
Message-ID: <42666F5D.4020800@gentoo.org> (raw)
In-Reply-To: <BAY13-F11346E27B7382CBEDA8D53D82B0@phx.gbl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
james osburn wrote:
>
> is the appropriate forum to ask about the uclibc stages?
> thanks
> jim
>
>
I'd imagine the embedded mailing list would be.
http://www.gentoo.org/main/en/lists.xml
- --
Bork Bork Bork!
Aaron Walker <ka0ttic@gentoo.org>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCZm9dC3poscuANHARAr+DAJ4gsaj/8RJgAH5AVrV0mWZS3kDd0wCgwmVc
LG95qg9Ii1gJFdYTPUJPQBo=
=pRnV
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-04-20 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 14:44 [gentoo-dev] is the appropriate forum to ask about the uclibc stages? james osburn
2005-04-20 15:03 ` Aaron Walker [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=42666F5D.4020800@gentoo.org \
--to=ka0ttic@gentoo.org \
--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