From: David Kastrup <dak@gnu.org>
Subject: Re: CVS Emacs vs. Mac OS X
Date: 27 Dec 2003 23:20:57 +0100 [thread overview]
Message-ID: <x5u13l2986.fsf@lola.goethe.zz> (raw)
In-Reply-To: 8765g23p0d.fsf@emptyhost.emptydomain.de
Kai Grossjohann <kai@emptydomain.de> writes:
> Joe Corneli <jcorneli@math.utexas.edu> writes:
>
> > make[1]: *** No rule to make target `regex.h', needed by `dired.o'. Stop.
>
> After the Savannah compromise, there have been system changes. This
> caused regex.h and regex.c to go away.
>
> In the meantime, the problem has been corrected. Please try "cvs up
> -dP" and try again.
>
> It is useful to read the emacs-devel list if you want to use the CVS
> version of Emacs. Yes, it's some amount of traffic, but with Gnus and
> scoring it should be manageable.
Sort it into a group of its own, that's what I do. Customizing
nnmail-split-methods is easy enough.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2003-12-27 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AVt2c-0006es-Ln@monty-python.gnu.org>
2003-12-27 6:53 ` CVS Emacs vs. Mac OS X Joe Corneli
[not found] ` <mailman.668.1072511850.868.help-gnu-emacs@gnu.org>
2003-12-27 21:54 ` Kai Grossjohann
2003-12-27 22:20 ` David Kastrup [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=x5u13l2986.fsf@lola.goethe.zz \
--to=dak@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).