From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Please pretest Emacs 21.3
Date: Mon, 27 May 2002 11:58:29 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1020527115536.8061C-100000@is> (raw)
In-Reply-To: <buo8z66xaxr.fsf@mcspd15.ucom.lsi.nec.co.jp>
On 27 May 2002, Miles Bader wrote:
> I notice that the RC for 21.3 contains the lisp reference manual (in the
> lispref/ subdir), but neither Makefile.in nor configure.in contain any
> rules for dealing with it (whereas the CVS head versions do).
>
> Is this intentional?
It's not intentional, but I don't know how to prevent this from
happening. The problems seems to be that, once a directory exists on
the trunk, it will exist on the branches as well.
The branch version of make-dist makes sure the lispref directory is not
present in the tarball, so the lack of Makefile's doesn't matter for the
users.
If someone can tell how to persuade CVS not to make lispref visible on
the branch, I'd be grateful.
next prev parent reply other threads:[~2002-05-27 8:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 1:54 Please pretest Emacs 21.3 Richard Stallman
2002-05-27 5:29 ` Eli Zaretskii
2002-05-27 9:49 ` Andreas Schwab
2002-05-27 10:04 ` nferrier
2002-05-27 10:04 ` Andreas Schwab
2002-05-27 10:26 ` nferrier
2002-05-27 11:30 ` nferrier
2002-05-27 11:06 ` Eli Zaretskii
2002-05-27 12:58 ` Andreas Schwab
2002-05-30 1:52 ` D. Goel
2002-05-30 2:26 ` Miles Bader
2002-05-30 2:59 ` D. Goel
2002-05-30 5:15 ` Eli Zaretskii
2002-05-30 2:43 ` D. Goel
2002-05-30 3:18 ` Miles Bader
2002-05-30 3:54 ` D. Goel
2002-05-30 4:11 ` Miles Bader
2002-05-30 5:19 ` Eli Zaretskii
2002-05-30 5:18 ` Eli Zaretskii
2002-05-27 6:29 ` Miles Bader
2002-05-27 7:19 ` Eli Zaretskii
2002-05-27 7:25 ` Miles Bader
2002-05-27 7:39 ` Eli Zaretskii
2002-05-27 8:16 ` Miles Bader
2002-05-27 8:58 ` Eli Zaretskii [this message]
2002-05-27 9:43 ` Andreas Schwab
2002-05-27 11:04 ` Eli Zaretskii
2002-05-27 11:09 ` Andreas Schwab
2002-05-27 11:14 ` Eli Zaretskii
2002-05-28 19:35 ` Stefan Monnier
2002-05-28 15:40 ` Kai Großjohann
2002-05-28 22:08 ` Fonts and Latin-15 Alex Schroeder
2002-05-29 7:33 ` Kai Großjohann
2002-05-29 11:10 ` Stefan Monnier
2002-05-29 12:59 ` Miles Bader
2002-05-29 13:21 ` Stefan Monnier
2002-05-30 17:04 ` Richard Stallman
2002-05-28 22:11 ` Please pretest Emacs 21.3 Alex Schroeder
2002-05-30 13:48 ` Juanma Barranquero
2002-06-12 9:32 ` Jason Rumney
2002-06-13 6:51 ` Juanma Barranquero
2002-06-13 7:24 ` Juanma Barranquero
[not found] <E17CHlK-0007nQ-00@fencepost.gnu.org>
2002-05-27 15:01 ` Andre Spiegel
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=Pine.SUN.3.91.1020527115536.8061C-100000@is \
--to=eliz@is.elta.co.il \
--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).