All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cort Dougan <cort@ppc.kernel.org>
To: "sean o'malley" <somalley@ed.mde.state.mi.us>
Cc: Nathan Hurst <njh@drongo.anu.edu.au>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Apple Job Posting and Good News for LinuxPPC developers
Date: Sat, 27 Mar 1999 22:08:07 -0700	[thread overview]
Message-ID: <19990327220807.A850@persephone.ppc.kernel.org> (raw)
In-Reply-To: <v04003a01b3213f280c3f@[204.22.210.180]>; from sean o'malley on Fri, Mar 26, 1999 at 01:51:31PM +0000


Look at this thing from what Apple has done in the past.  This just means
Linux is the Apple OS of the week.  They don't have a good track record
with keeping with their plans.

} It sounded like it was more political and PR based than actual development.
} Im wondering if it would entail a whole department/unit with multiple
} people.  Maybe  a couple of developers to help solve some of the more nasty
} stuff , a pr person to help promote linuxppc and our efforts (judging from
} some of the stuff RHS has been saying he isnt to aware of our project or

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-03-28  5:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-14 13:35 Blue G3 and machine check Benjamin Herrenschmidt
1999-03-15 16:42 ` Ryuichi Oikawa
1999-03-15 17:09   ` Geert Uytterhoeven
1999-03-24  9:30 ` Gabriel Paubert
1999-03-24 23:12   ` Paul Mackerras
1999-03-25 11:20     ` Gabriel Paubert
1999-03-25 16:46       ` Apple Job Posting and Good News for LinuxPPC developers Kevin B. Hendricks
1999-03-25 19:12         ` David Edelsohn
1999-03-26 11:31           ` Gabriel Paubert
1999-03-26 16:13             ` David Edelsohn
1999-03-27  6:27               ` Guy Sotomayor
1999-03-27 20:44                 ` David Edelsohn
1999-04-02 12:11             ` Holger Bettag
1999-04-02 17:11               ` David Edelsohn
1999-04-02 22:19                 ` Douglas Godfrey
1999-04-03 17:42                 ` Holger Bettag
1999-04-05 16:11                   ` Gabriel Paubert
1999-04-05 16:06               ` Gabriel Paubert
1999-04-06  5:53                 ` Douglas Godfrey
1999-03-26  6:08         ` Nathan Hurst
1999-03-26 13:51           ` sean o'malley
1999-03-28  5:08             ` Cort Dougan [this message]
1999-03-26 20:33           ` N.G. Temme
1999-03-29 23:44       ` Blue G3 and machine check Paul Mackerras
1999-03-30 11:41         ` Gabriel Paubert
1999-03-31 16:20           ` Ryuichi Oikawa
1999-03-31 18:39             ` Gabriel Paubert
1999-04-05 16:36               ` Ryuichi Oikawa
1999-04-05 17:11                 ` Gabriel Paubert
1999-04-04  1:17             ` Joel Klecker
1999-04-09  5:58               ` Joel Klecker
1999-04-09 16:12                 ` Ryuichi Oikawa
1999-03-25 12:10     ` Benjamin Herrenschmidt

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=19990327220807.A850@persephone.ppc.kernel.org \
    --to=cort@ppc.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=njh@drongo.anu.edu.au \
    --cc=somalley@ed.mde.state.mi.us \
    /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.