From: Eli Zaretskii <eliz@is.elta.co.il>
To: "J.T. Conklin" <jtc@redback.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: make capabilities
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010306105535.7922I-100000@is> (raw)
In-Reply-To: <5mg0gsrn5x.fsf@jtc.redback.com>
On 5 Mar 2001, J.T. Conklin wrote:
> Eli> 1. The current Emacs distribution uses $(FOO:.x=.y) in its Makefile's.
> Eli> While this version is not yet released, its pretest was tested on
> Eli> many different systems, and none failed to build it.
>
> Good to hear. I'd feel more comfortable if it had been released and there
> weren't any recorded complaints.
That makes two of us (I was the one who asked the Emacs head
maintainer to use this construct instead of invoking Sed).
Anyway, the Emacs 21 pretest is taking such a long time and draining
so much of my resources that I really wish it was over ;-)
prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 J.T. Conklin
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Eli Zaretskii [this message]
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.SUN.3.91.1010306105535.7922I-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sourceware.cygnus.com \
--cc=jtc@redback.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).