From: Iruata Souza <iru.muzgo@gmail.com>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ports duplication
Date: Mon, 8 Mar 2010 09:17:39 -0300 [thread overview]
Message-ID: <d1c554291003080417m60acaa99t950e5b0a44c0fe39@mail.gmail.com> (raw)
In-Reply-To: <f3b464f6818265b05e2fbdf20db8cc59@proxima.alt.za>
On Mon, Mar 8, 2010 at 1:26 AM, <lucio@proxima.alt.za> wrote:
>> As for the smaller things, I would prefer to see ten different bits of
>> code that achieve the same end vs. just one. Diversity is good, and a
>> broader selection of code gives a bigger field to mine for ideas and
>> concepts.
>
> I really don't think that's going to be the problem here, we do not
> have an excess of ports, we have a problem determining whether a port
> exists or,
i don't think we have that problem if the port in in sources. you may
have it because you don't seem to use fgb/contrib or any other tool
for that.
> It also helps a lot if one can establish a level of confidence in a
> port,
what would that level be?
iru
prev parent reply other threads:[~2010-03-08 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 19:49 Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-07 20:02 ` Eric Van Hensbergen
2010-03-08 4:26 ` lucio
2010-03-08 12:17 ` Iruata Souza [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=d1c554291003080417m60acaa99t950e5b0a44c0fe39@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).