From: Karim Yaghmour <karim@domain.hid>
To: Pradeep Padala <ppadala@domain.hid>
Cc: Frederik Deweerdt <dev.deweerdt@domain.hid>, adeos-main@gna.org
Subject: Re: [Adeos-main] adeos-devel
Date: Tue, 04 Jun 2002 11:47:28 -0400 [thread overview]
Message-ID: <3CFCE110.6574C3E3@domain.hid> (raw)
In-Reply-To: Pine.GSO.4.05.10206041133530.25280-100000@domain.hid
Hello Pradeep,
As I was saying ... we've barely had the time to breath ... we'll definitely
get to a to-do ... Meanwhile, have you had a chance to look at the 5 items
we were mentionning the technical announcement? ... I think I'll post of this
message to this list right now so that there be at least a copy of it in
the project's mail archives ... Items such as having 2 Linux kernels running
side-by-side on Adeos would be of prime interest to all Linux users. This
would be really neat because this is the kind of stuff that is only
available on very expensive high-end IBM mainframes. Enabling this with
standard PC hardware would be very useful to many folks.
Karim
Pradeep Padala wrote:
>
> Hi Karim,
>
> > The sourceforge space is now obsolete. There never was any code there
> > and any new development is going to be done on the Savannah
> > workspace.
>
> I would like to participate in the development. I haven't seen any
> todo list in the cvs though. Can you point out your immediate goals
> for adeos and some guidance of where to start and what to start?
>
> --pradeep
--
===================================================
Karim Yaghmour
karim@domain.hid
Embedded and Real-Time Linux Expert
===================================================
prev parent reply other threads:[~2002-06-04 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 14:44 [Adeos-main] adeos-devel Frederik Deweerdt
2002-06-04 15:02 ` Karim Yaghmour
2002-06-04 15:38 ` Pradeep Padala
2002-06-04 15:47 ` Karim Yaghmour [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=3CFCE110.6574C3E3@domain.hid \
--to=karim@domain.hid \
--cc=adeos-main@gna.org \
--cc=dev.deweerdt@domain.hid \
--cc=ppadala@domain.hid \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.