From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: David Edelsohn <edelsohn@gnu.org>
Cc: <gcc@gcc.gnu.org>
Subject: Moving AIX-related patch to doc/install.texi to the 3.0-branch?
Date: Sat, 15 Sep 2001 05:10:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.33.0109151407120.87618-100000@taygeta.dbai.tuwien.ac.at> (raw)
Dear David,
I'm sorry that I missed that when you installed the following patch
2001-09-07 David Edelsohn <edelsohn@gnu.org>
* rs6000.c (num_insns_constant): Compute number of instructions
more accurately.
* doc/install.texi: Explain AIX exception handling work-around.
Update URL for AIX fixes.
but I believe the doc/install.texi patch probably should be go to the
3.0-branch as well.
If you, as rs6000 maintainer, agree, would you mind making this move?
Thanks,
Gerald
PS: Usually I've had sent this in private, but if it's really desirable
to send all such notes to public lists, I can do that. Thoughts?
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
reply other threads:[~2001-09-15 5:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.BSF.4.33.0109151407120.87618-100000@taygeta.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=edelsohn@gnu.org \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).