public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: geoffk@ozemail.com.au
Cc: gavin@cygnus.com, mark@codesourcery.com, binutils@sourceware.cygnus.com
Subject: Re: Reloc changes to bfd/elf32-mips.c
Date: Mon, 27 Sep 1999 18:25:00 -0000	[thread overview]
Message-ID: <19990928012444.5094.qmail@daffy.airs.com> (raw)
In-Reply-To: <199909271119.VAA01664@gluttony.geoffk.wattle.id.au>

   Date: Mon, 27 Sep 1999 21:19:26 +1000
   From: Geoff Keating <geoffk@ozemail.com.au>

   This has most impact on C++.

   I'm not sure exactly who can approve changes to the sourceware
   binutils; if Gavin or Mark could do this (at least for MIPS), it'd be
   good to know as the current sequence of patches will not be the last.
   I'm also not sure who can check stuff in.

   Anyway, is the patch OK?

This patch is OK with me.

Ian

  reply	other threads:[~1999-09-27 18:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27  4:24 Geoff Keating
1999-09-27 18:25 ` Ian Lance Taylor [this message]
1999-09-27  4:30 Geoff Keating
1999-09-27 12:37 ` Mark Mitchell
1999-09-28  0:54 ` Mark Mitchell
1999-09-28  6:57   ` Ian Lance Taylor
1999-09-28 20:32   ` Geoff Keating
1999-09-28 20:57     ` Ian Lance Taylor
1999-09-28 21:52       ` Geoff Keating
1999-09-28 22:03         ` Ian Lance Taylor
1999-10-06 19:21           ` Geoff Keating
1999-10-06 19:35             ` Ian Lance Taylor
1999-10-06 20:39               ` Geoff Keating
1999-10-06 20:53                 ` Ian Lance Taylor
1999-10-07  4:47                   ` Geoff Keating
1999-10-07  7:28                     ` Ian Lance Taylor
1999-10-07  9:17                     ` Mark Mitchell
1999-09-28 22:16     ` Mark Mitchell
1999-09-29  8:25       ` Ian Lance Taylor

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=19990928012444.5094.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=gavin@cygnus.com \
    --cc=geoffk@ozemail.com.au \
    --cc=mark@codesourcery.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).