From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: admin/make-tarball.txt instructs to commit lisp/loaddefs.el.
Date: Fri, 15 Apr 2005 11:20:31 +0300 [thread overview]
Message-ID: <01c54194$Blat.v2.4$22522060@zahav.net.il> (raw)
In-Reply-To: <87oechwxcb.fsf@xs4all.nl> (message from Lute Kamstra on Thu, 14 Apr 2005 10:56:20 +0200)
> From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
> Date: Thu, 14 Apr 2005 10:56:20 +0200
>
> 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?
I think the right replacememnt is to say this:
. Copy lisp/loaddefs.el into lisp/ldefs-boot.el
. Commit lisp/ldefs-boot.el
next prev parent reply other threads:[~2005-04-15 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 8:56 admin/make-tarball.txt instructs to commit lisp/loaddefs.el Lute Kamstra
2005-04-15 8:20 ` Eli Zaretskii [this message]
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='01c54194$Blat.v2.4$22522060@zahav.net.il' \
--to=eliz@gnu.org \
--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).