From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: src/deps.mk
Date: Fri, 04 Feb 2011 20:31:14 +0200 [thread overview]
Message-ID: <83vd0zabyl.fsf@gnu.org> (raw)
In-Reply-To: <4D4C1F70.8040903@cs.ucla.edu>
> Date: Fri, 04 Feb 2011 07:46:56 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: emacs-devel@gnu.org
>
> configure.in says that it's used by all platforms
> except for those that combine GNU Make, GCC, and
> use autodepend. So it would appear that a lot of
> platforms use it, e.g., plain Solaris.
I asked because it seemed strange that no one reported any problems
with the obviously stale prerequisites. I guess there aren't many
users of these systems who track the development trunk.
prev parent reply other threads:[~2011-02-04 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 12:07 src/deps.mk Eli Zaretskii
2011-02-04 15:46 ` src/deps.mk Paul Eggert
2011-02-04 18:31 ` 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
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=83vd0zabyl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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).