Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Keith M Wesolowski <wesolows@foobazco.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: Question on the binutils tradlittlemips patch
Date: Mon, 23 Apr 2001 00:34:40 -0400	[thread overview]
Message-ID: <20010423003440.A20179@nevyn.them.org> (raw)
In-Reply-To: <20010422212301.B6180@foobazco.org>; from wesolows@foobazco.org on Sun, Apr 22, 2001 at 09:23:01PM -0700

On Sun, Apr 22, 2001 at 09:23:01PM -0700, Keith M Wesolowski wrote:
> On Sun, Apr 22, 2001 at 10:19:53PM -0400, Daniel Jacobowitz wrote:
> 
> > I have them working in the case I care about - no backwards
> > compatibility at all.  We (Monta Vista) can get away with this :)
> > I've attached the patches.
> 
> This looks like what I have come up with as well.  I don't care about
> backward compatibility either.  If someone else wants to support
> broken crap that's their problem; in an age where we have scripts and
> makefiles to rebuild entire systems from source I can't see the point
> of binary compatibility.

Don't you wish?  My other hat is Debian, which can't just ditch
existing MIPS installations like that.

-- 
Daniel Jacobowitz                           Debian GNU/Linux Developer
Monta Vista Software                              Debian Security Team

  reply	other threads:[~2001-04-23  4:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 18:19 Question on the binutils tradlittlemips patch Daniel Jacobowitz
2001-04-18 20:11 ` Andreas Jaeger
2001-04-18 21:03   ` Daniel Jacobowitz
2001-04-18 20:47 ` Steven J. Hill
2001-04-18 20:37   ` Daniel Jacobowitz
2001-04-23  1:07     ` Keith M Wesolowski
2001-04-23  2:19       ` Daniel Jacobowitz
2001-04-23  4:23         ` Keith M Wesolowski
2001-04-23  4:34           ` Daniel Jacobowitz [this message]
2001-04-23  5:54             ` Andreas Jaeger

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=20010423003440.A20179@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=wesolows@foobazco.org \
    /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