From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: rms@gnu.org, eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: NT Emacs make problem..
Date: Tue, 11 Jun 2002 21:29:39 +0200 [thread overview]
Message-ID: <vafn0u1k40s.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <ap3lm9lhhac.fsf@student1.physics.umd.edu> ("D. Goel"'s message of "11 Jun 2002 13:11:23 -0400")
"D. Goel" <deego@glue.umd.edu> writes:
> Cool, we are done with this file then :). I am including the file at
> the end of this mail. perhaps, Could the maintainers please install it?
I still think it would be useful to say something about "make
bootstrap". Suggestion A (to be appended to the previous text):
Normally, it is not necessary to use "make bootstrap" after every CVS
update. Unless there are problems, "make all" should be used.
Suggestion B (also for append):
Note that "make bootstrap" overwrites some files which are under CVS
control (in particular, lisp/loaddefs.el and lisp/cus-load.el). So
subsequent CVS updates might lead to CVS conflicts. If such a
conflict arises, just overwrite your copy of the file with a clean
copy from the CVS repository, for example by issuing the following
command:
cvs update -C lisp/cus-load.el
It's not clear to me which of the two suggestions should go in, but
at least one of them appears useful. (Maybe you want both.)
Opinions?
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-06-11 19:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SUN.3.91.1020605143252.7779A-100000@is>
[not found] ` <ap3bsapg081.fsf@student1.physics.umd.edu>
[not found] ` <9735-Wed05Jun2002210858+0300-eliz@is.elta.co.il>
2002-06-07 0:44 ` NT Emacs make problem Richard Stallman
2002-06-07 1:11 ` Thien-Thi Nguyen
2002-06-08 19:15 ` Richard Stallman
2002-06-08 20:20 ` Thien-Thi Nguyen
2002-06-10 10:15 ` Richard Stallman
2002-06-10 10:39 ` Thien-Thi Nguyen
2002-06-11 17:16 ` D. Goel
2002-06-07 13:37 ` Eli Zaretskii
2002-06-07 14:09 ` D. Goel
2002-06-07 15:07 ` Simon Josefsson
2002-06-07 16:47 ` D. Goel
2002-06-08 19:15 ` Richard Stallman
2002-06-09 3:11 ` D. Goel
2002-06-10 10:14 ` Richard Stallman
2002-06-10 11:34 ` Kai Großjohann
2002-06-11 17:11 ` D. Goel
2002-06-11 19:29 ` Kai Großjohann [this message]
2002-06-12 12:14 ` Richard Stallman
2002-06-12 13:13 ` Stefan Monnier
2002-06-13 4:55 ` Eli Zaretskii
2002-06-13 21:46 ` Richard Stallman
2002-06-12 13:37 ` Kai Großjohann
2002-06-13 21:47 ` Richard Stallman
2002-06-12 14:33 ` Andreas Schwab
2002-06-13 14:36 ` D. Goel
2002-06-12 2:34 ` Richard Stallman
2002-06-12 4:48 ` Eli Zaretskii
2002-06-12 12:42 ` Richard Stallman
2002-06-12 8:28 ` Simon Josefsson
2002-06-09 15:48 ` Kai Großjohann
2002-06-09 22:44 ` Kim F. Storm
2002-06-10 23:44 ` Richard Stallman
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=vafn0u1k40s.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.