From: Miguel de Icaza <miguel@nuclecu.unam.mx>
To: ariel@cthulhu.engr.sgi.com
Cc: davem@dm.cobaltmicro.com, ralf@uni-koblenz.de,
ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com,
adevries@engsoc.carleton.ca, richard@infopact.nl
Subject: Re: linus.linux.sgi.com
Date: Mon, 18 Jan 1999 11:25:00 -0600 [thread overview]
Message-ID: <199901181725.LAA20930@metropolis.nuclecu.unam.mx> (raw)
In-Reply-To: <199901181040.CAA33736@oz.engr.sgi.com> (ariel@oz.engr.sgi.com)
> The binary compatibility FUD is ironic considering
> that they have broken binary compatibility as well as source
> compatibility so many times in their history (m68k -> SPARC
> SPARC - x86, SunOs -> Solaris) believe me I know since I've
> been a Sun customer and an ISV.
You forgot the breakage in the various Solaris 2.n->2.n+1
At least the 2.4->2.5 was painful for me
Miguel.
WARNING: multiple messages have this Message-ID (diff)
From: Miguel de Icaza <miguel@nuclecu.unam.mx>
To: ariel@cthulhu.engr.sgi.com
Cc: davem@dm.cobaltmicro.com, ralf@uni-koblenz.de,
linux@cthulhu.engr.sgi.com, adevries@engsoc.carleton.ca,
richard@infopact.nl
Subject: Re: linus.linux.sgi.com
Date: Mon, 18 Jan 1999 11:25:00 -0600 [thread overview]
Message-ID: <199901181725.LAA20930@metropolis.nuclecu.unam.mx> (raw)
Message-ID: <19990118172500.yc1kJ_gLp1pCqkpA6lxM6e94VXGAVCd-oLLzfGzlX84@z> (raw)
In-Reply-To: <199901181040.CAA33736@oz.engr.sgi.com> (ariel@oz.engr.sgi.com)
> The binary compatibility FUD is ironic considering
> that they have broken binary compatibility as well as source
> compatibility so many times in their history (m68k -> SPARC
> SPARC - x86, SunOs -> Solaris) believe me I know since I've
> been a Sun customer and an ISV.
You forgot the breakage in the various Solaris 2.n->2.n+1
At least the 2.4->2.5 was painful for me
Miguel.
next prev parent reply other threads:[~1999-01-18 17:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-15 18:24 linus.linux.sgi.com Alex deVries
1999-01-15 18:28 ` linus.linux.sgi.com Eric Kimminau
1999-01-15 18:44 ` linus.linux.sgi.com Richard Hartensveld
1999-01-15 19:09 ` linus.linux.sgi.com Ariel Faigon
1999-01-15 19:09 ` linus.linux.sgi.com Ariel Faigon
1999-01-15 21:29 ` linus.linux.sgi.com Alan Cox
1999-01-15 21:59 ` linus.linux.sgi.com ralf
1999-01-16 3:21 ` linus.linux.sgi.com David S. Miller
1999-01-18 10:40 ` linus.linux.sgi.com Ariel Faigon
1999-01-18 10:40 ` linus.linux.sgi.com Ariel Faigon
1999-01-18 17:25 ` Miguel de Icaza [this message]
1999-01-18 17:25 ` linus.linux.sgi.com Miguel de Icaza
1999-01-19 4:40 ` linus.linux.sgi.com Eric Kimminau
1999-01-19 5:19 ` linus.linux.sgi.com David S. Miller
1999-01-19 11:21 ` linus.linux.sgi.com dmanddmer
1999-01-19 15:30 ` linus.linux.sgi.com David Watters
1999-01-19 16:46 ` linus.linux.sgi.com Alex deVries
1999-01-19 15:05 ` linus.linux.sgi.com David Watters
1999-01-15 22:38 ` linus.linux.sgi.com Miguel de Icaza
1999-01-15 22:06 ` linus.linux.sgi.com William J. Earl
-- strict thread matches above, loose matches on Subject: below --
1999-01-28 22:07 linus.linux.sgi.com Ulf Carlsson
1999-01-23 2:07 linus.linux.sgi.com ralf
1998-06-14 20:35 linus.linux.sgi.com Alex deVries
1998-06-15 18:02 ` linus.linux.sgi.com Bob Mende Pie
1998-06-15 18:11 ` linus.linux.sgi.com Alex deVries
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=199901181725.LAA20930@metropolis.nuclecu.unam.mx \
--to=miguel@nuclecu.unam.mx \
--cc=adevries@engsoc.carleton.ca \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=davem@dm.cobaltmicro.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
--cc=richard@infopact.nl \
/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.