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: Boring new tests for mips gas.
Date: Mon, 27 Sep 1999 18:34:00 -0000	[thread overview]
Message-ID: <19990928013351.5183.qmail@daffy.airs.com> (raw)
In-Reply-To: <199909271121.VAA01667@gluttony.geoffk.wattle.id.au>

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

   Just some random tests.  They'd be more interesting if they failed.

   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.

As far as I'm concerned, Richard Henderson and I can approve any
change (I haven't heard from Ken Raeburn in a while).  There are
various people who can check changes in, including Richard, me, Mark,
and a number of people at Cygnus.  It's easy to add you to the list of
people who can check stuff in after approval if you like.  In fact, I
see that you are already on that list.

   Anyway, is the patch OK?

This patch is OK, except: 1) you add a new file empic.d, which does
not appear to be used; 2) the file names elf-reloc.s and elf-reloc-2.s
will be the same on an 8.3 file system; use different names, rather
than introduce additional 8.3 file name problems.  Use the doschk
program to make sure they are OK.

Ian

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27  4:27 Geoff Keating
1999-09-27 18:34 ` Ian Lance Taylor [this message]
1999-10-06 19:19   ` Geoff Keating
1999-10-06 19:26     ` Ian Lance Taylor
1999-10-06 19:28     ` DJ Delorie

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=19990928013351.5183.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).