From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Announcing announcing work effort. [Was: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?]
Date: Fri, 11 May 2007 07:53:10 +0200 [thread overview]
Message-ID: <5d375e920705102253i503da22cq210ccac37ff74757@mail.gmail.com> (raw)
In-Reply-To: <32a656c20705102246m26c72ecfxba277a9d5112f1d2@mail.gmail.com>
It is very easy: get people to use 9fs(1) and cp(1), this is not rocket science!
I could even do without announcements and having people that releases
source remain anonymous if they don't want to bother answering
questions about it, I think it is silly, but as long as the code is
out there and when someone asks me "I would like to work on XXX" I can
at least point them to "you can find the latest code for XXX over
there" I'm happy.
By the way, I just was told apparently there is a working AC97 driver
(no, not the one from the CMU guys, who apparently seems are
duplicating existing work.)
uriel
On 5/11/07, Vester Thacker <vester.thacker@gmail.com> wrote:
> On 5/11/07, Uriel <uriel99@gmail.com> wrote:
> >
> > Or is asking people to do 9fs + cp(1) too much? Of course it would be
> > better if people actually posted a short comment about their work to
> > 9fans, but I can do even without that as long as people puts the
> > damned code somewhere where others can find it.
>
> Let me see if I got the problems right. Many people do not announce
> their work. A number of people don`t post their work on sources. If
> so, then what can be done to improve the each situation? Any takers?
>
> Regards,
> Vester
>
prev parent reply other threads:[~2007-05-11 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 5:46 Vester Thacker
2007-05-11 5:53 ` Uriel [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=5d375e920705102253i503da22cq210ccac37ff74757@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/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).