unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Subject: admin/make-tarball.txt instructs to commit lisp/loaddefs.el.
Date: Thu, 14 Apr 2005 10:56:20 +0200	[thread overview]
Message-ID: <87oechwxcb.fsf@xs4all.nl> (raw)

admin/make-tarball.txt instructs to commit lisp/loaddefs.el, but this
file is no longer in the repository.  Would committing lisp/ldefs-boot.el
be the right replacement?

Lute.


Index: admin/make-tarball.txt
===================================================================
RCS file: /cvsroot/emacs/emacs/admin/make-tarball.txt,v
retrieving revision 1.13
diff -c -r1.13 make-tarball.txt
*** admin/make-tarball.txt	6 Feb 2005 22:32:31 -0000	1.13
--- admin/make-tarball.txt	14 Apr 2005 08:49:38 -0000
***************
*** 21,30 ****
  
  5.   rm configure; make bootstrap
  
! 6.  Commit configure, README, AUTHORS, lisp/loaddefs.el,
!     lisp/cus-load.el, lisp/finder-inf.el, lisp/version.el,
!     man/emacs.texi.  For a release, also commit the ChangeLog files in
!     all directories.
  
  7.   make-dist --snapshot.  Check the contents of the new tar with
       admin/diff-tar-files against an older tar file.  Some old pretest
--- 21,31 ----
  
  5.   rm configure; make bootstrap
  
! 6.  Commit configure, README, AUTHORS, lisp/cus-load.el,
!     lisp/finder-inf.el, lisp/version.el, man/emacs.texi.
!     Copy lisp/loaddefs.el to lisp/ldefs-boot.el and commit
!     lisp/ldefs-boot.el.  For a release, also commit the ChangeLog
!     files in all directories.
  
  7.   make-dist --snapshot.  Check the contents of the new tar with
       admin/diff-tar-files against an older tar file.  Some old pretest

             reply	other threads:[~2005-04-14  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14  8:56 Lute Kamstra [this message]
2005-04-15  8:20 ` admin/make-tarball.txt instructs to commit lisp/loaddefs.el Eli Zaretskii
2005-04-15  8:36   ` Lute Kamstra

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=87oechwxcb.fsf@xs4all.nl \
    --to=lute.kamstra.lists@xs4all.nl \
    /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).