From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New Category - dev-pic OR dev-embedded
Date: 17 Oct 2003 16:48:18 -0400 [thread overview]
Message-ID: <1066423698.2582.2531.camel@simple> (raw)
In-Reply-To: <20031017190642.GC29647@curie-int.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Robin,
Why not help move forward with what's leftover of the #gentoo-embedded
project. I'm what you will learn over the course of this class would be
suited for such a place.
There is a few of us already even in the irc channel few months now. It
just needs some leadership.
As for a new category I'm sorta opposed. uClibc, busybox and the such
are placed in existing categories and I'm pretty sure of the 102
existing ones a place could be found for this. The more new top level
categories we add the slower portage gets..
However feel free to ignore me, I might not know what I'm talking about.
On Fri, 2003-10-17 at 15:06, Robin H. Johnson wrote:
> On Fri, Oct 17, 2003 at 12:05:01PM -0700, Robin H. Johnson wrote:
> > Support Reasoning: I've got a class on programming PIC16F87[47] chips
> > this semester, and I really don't want to use the nasty windows programs
> > to build my code. And since I've got access to the hardware, might as
> > well test out the code that should work to get it into the tree.
> I'll be making a herd 'dev-pic' or whatever the category name is to keep
> track of all the bugs for this once it's approved.
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux Developer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2003-10-17 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 19:05 [gentoo-dev] New Category - dev-pic OR dev-embedded Robin H. Johnson
2003-10-17 19:06 ` Robin H. Johnson
2003-10-17 20:48 ` Ned Ludd [this message]
2003-10-18 0:46 ` Robin H. Johnson
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=1066423698.2582.2531.camel@simple \
--to=solar@gentoo.org \
--cc=gentoo-dev@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