From: Alan Modra <amodra@bigpond.net.au>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Fix cgen warnings in opcodes/
Date: Mon, 02 Dec 2002 14:06:00 -0000 [thread overview]
Message-ID: <20021202220558.GI27956@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <20021202185356.GC11925@redhat.com>
On Mon, Dec 02, 2002 at 01:53:57PM -0500, Frank Ch. Eigler wrote:
> > (cgen-desc.c): Include regex.h.
>
> I think this is supposed to be xregex.h, referring to libiberty's
> snapshot of glibc regex.
Fixed and applied. It wasn't clear that you were approving the
cgen/opc-opinst.scm and cgen/cpu/openrisc.opc changes so they're
not in yet.
Before committing, I updated the copyright dates and noticed that
some files were copyright Redhat. Should this be changed to
Free Software Foundation?
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2002-12-02 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 22:59 Alan Modra
2002-12-02 4:57 ` Alan Modra
2002-12-02 10:53 ` Frank Ch. Eigler
2002-12-02 14:06 ` Alan Modra [this message]
2002-12-02 14:27 ` Frank Ch. Eigler
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=20021202220558.GI27956@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.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).