From: Jesper Harder <harder@myrealbox.com>
Subject: Re: more CVS trouble
Date: Wed, 07 Jan 2004 22:08:39 +0100 [thread overview]
Message-ID: <m3r7yba2lk.fsf@defun.localdomain> (raw)
In-Reply-To: mailman.170.1073511825.928.help-gnu-emacs@gnu.org
Joe Corneli <jcorneli@math.utexas.edu> writes:
> and got these results upon running ./configure && make bootstrap
>
> make[1]: Leaving directory `/home/jcorneli/emacs/leim'
> (cd man; make info)
> make[1]: Entering directory `/home/jcorneli/emacs/man'
> cd /home/jcorneli/emacs/man; makeinfo emacs.texi
> emacs.texi:10: Unknown command `copying'.
> emacs.texi:31: Unmatched `@end'.
You need a more recent version of Texinfo.
next prev parent reply other threads:[~2004-01-07 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Aas6o-0005EM-Jk@monty-python.gnu.org>
2004-01-07 20:41 ` more CVS trouble Joe Corneli
[not found] ` <mailman.170.1073511825.928.help-gnu-emacs@gnu.org>
2004-01-07 21:08 ` Jesper Harder [this message]
2004-01-17 20:06 ` Kai Grossjohann
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=m3r7yba2lk.fsf@defun.localdomain \
--to=harder@myrealbox.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).