From: Ralf Fassel <ralf@akutech.de>
Cc: drk@sgi.com, rms@gnu.org, bug-gnu-emacs@gnu.org
Subject: Re: `print' does not print
Date: Fri, 12 Apr 2002 13:31:46 +0200 [thread overview]
Message-ID: <a96nji$ofv$2@main.gmane.org> (raw)
In-Reply-To: <1659-Fri12Apr2002123712+0300-eliz@is.elta.co.il>
* Eli Zaretskii
| It is my impression that removing the SGI-specific treatment of the
| `.got' sections from unexelf.c is a good idea, but I'm unsure
| whether it will have adverse effects on some (older?) versions of
| the SGI development tools, and if so whether saying in etc/MACHINES
| that users should upgrade to newer devo is good enough.
Since we do not seem to be able to recreate the exact conditions to
check why these were necessary (David?), and since an OS upgrade (Good
Thing [TM] anyway) solves the issue I have brought up, I think adding
advice to etc/MACHINES is enough.
R'
next prev parent reply other threads:[~2002-04-12 11:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200203202019.g2KKJfs4410490@jupiter.akutech-local.de>
[not found] ` <ap3lmcnkjy4.fsf@fosters.umd.edu>
2002-03-21 16:25 ` `print' does not print Eli Zaretskii
2002-03-21 17:10 ` D. Goel
2002-03-21 18:49 ` Ralf Fassel
2002-03-21 20:15 ` Ralf Fassel
2002-03-21 21:14 ` Ralf Fassel
2002-03-22 10:17 ` Eli Zaretskii
2002-03-22 10:41 ` Ralf Fassel
2002-03-22 11:58 ` Eli Zaretskii
2002-03-22 14:22 ` Ralf Fassel
2002-03-22 17:00 ` Eli Zaretskii
2002-03-22 17:47 ` Ralf Fassel
2002-03-22 18:35 ` Eli Zaretskii
2002-03-22 19:17 ` Ralf Fassel
2002-03-22 20:11 ` Eli Zaretskii
2002-03-22 22:18 ` Ralf Fassel
2002-03-23 8:54 ` Eli Zaretskii
2002-03-23 14:19 ` Ralf Fassel
2002-03-23 16:48 ` Eli Zaretskii
2002-03-23 17:10 ` Ralf Fassel
2002-03-22 20:44 ` Stefan Monnier
2002-03-23 16:13 ` Richard Stallman
2002-03-24 16:51 ` Ralf Fassel
2002-03-24 18:16 ` Eli Zaretskii
2002-03-24 20:22 ` Ralf Fassel
2002-03-25 6:02 ` Eli Zaretskii
2002-03-25 13:47 ` Ralf Fassel
2002-03-25 14:35 ` Eli Zaretskii
2002-03-25 14:49 ` David Kaelbling
2002-03-25 20:05 ` Eli Zaretskii
2002-03-25 20:15 ` David Kaelbling
2002-03-26 5:46 ` Eli Zaretskii
2002-03-26 14:20 ` David Kaelbling
2002-03-26 14:28 ` Eli Zaretskii
2002-03-26 14:43 ` Ralf Fassel
2002-03-25 17:41 ` Ralf Fassel
2002-03-25 17:55 ` David Kaelbling
2002-03-25 20:14 ` Eli Zaretskii
2002-03-25 21:33 ` Ralf Fassel
2002-03-26 5:48 ` Eli Zaretskii
2002-03-26 14:43 ` David Kaelbling
2002-03-26 17:30 ` Ralf Fassel
2002-03-27 5:49 ` Eli Zaretskii
2002-03-27 9:00 ` Ralf Fassel
2002-03-27 9:10 ` Eli Zaretskii
2002-04-12 9:37 ` Eli Zaretskii
2002-04-12 11:31 ` Ralf Fassel [this message]
[not found] ` <15542.50594.404120.372721@jupiter.akutech-local.de>
2002-04-12 15:08 ` David Kaelbling
2002-04-13 10:33 ` Eli Zaretskii
2002-04-13 10:52 ` Eli Zaretskii
2002-04-13 19:06 ` Richard Stallman
2002-03-25 12:01 ` Richard Stallman
2002-03-22 12:24 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a96nji$ofv$2@main.gmane.org' \
--to=ralf@akutech.de \
--cc=bug-gnu-emacs@gnu.org \
--cc=drk@sgi.com \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).