From: Po Lu <luangruo@yahoo.com>
To: emacs-devel@gnu.org
Cc: Gregory Heytings <gregory@heytings.org>
Subject: Re: master 3fd2b00a4b 2/2: ; * Makefile.in: Add "make bootstrap configure=default" as a first choice.
Date: Mon, 19 Sep 2022 15:46:29 +0800 [thread overview]
Message-ID: <87leqfrelm.fsf@yahoo.com> (raw)
In-Reply-To: <20220919074155.2E6D7C00872@vcs2.savannah.gnu.org> (Gregory Heytings's message of "Mon, 19 Sep 2022 03:41:55 -0400 (EDT)")
Gregory Heytings <gregory@heytings.org> writes:
> # ADVICE-ON-FAILURE-BEGIN:bootstrap
> # You might try to:
> +# - run "git bootstrap configure=default", to rebuild Emacs with the
> +# default configuration options, which might fix the problem
> # - run "git clean -fdx" and run "make bootstrap" again, which might
> -# fix the problem
> +# fix the problem if "git boostrap configure=default" did not
> # !BEWARE! "git clean -fdx" deletes all files that are not under
> # !BEWARE! version control, which means that all changes to such
> # !BEWARE! files will be lost and cannot be restored later
Excuse me, but what is "git bootstrap"? Trying that leads to:
git: 'bootstrap' is not a git command. See 'git --help'.
further more, it is definitely better to mention the bug tracker than to
not, which is what you keep removing with your changes.
It is also probably a bad idea to refer to git as a first choice,
because most people do not get Emacs from a repository checkout. Nor
are we guaranteed to be using Git 5, or 10 years in the future.
next parent reply other threads:[~2022-09-19 7:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166357331345.19427.12446846086384744693@vcs2.savannah.gnu.org>
[not found] ` <20220919074155.2E6D7C00872@vcs2.savannah.gnu.org>
2022-09-19 7:46 ` Po Lu [this message]
2022-09-19 7:52 ` master 3fd2b00a4b 2/2: ; * Makefile.in: Add "make bootstrap configure=default" as a first choice Gregory Heytings
2022-09-19 7:50 ` Lars Ingebrigtsen
2022-09-19 7:52 ` Po Lu
2022-09-19 7:53 ` Gregory Heytings
2022-09-19 7:59 ` Lars Ingebrigtsen
2022-09-19 8:01 ` Po Lu
2022-09-19 9:29 ` Gregory Heytings
2022-09-19 9:41 ` Lars Ingebrigtsen
2022-09-19 10:13 ` Stefan Kangas
2022-09-19 12:15 ` Stefan Monnier
2022-09-19 12:25 ` Po Lu
2022-09-19 12:33 ` Lars Ingebrigtsen
2022-09-19 12:51 ` Po Lu
2022-09-19 13:02 ` Stefan Monnier
2022-09-19 13:04 ` Lars Ingebrigtsen
2022-09-19 13:22 ` Gregory Heytings
2022-09-19 18:41 ` Lars Ingebrigtsen
2022-09-19 13:37 ` Po Lu
2022-09-19 14:02 ` Eli Zaretskii
2022-09-19 14:14 ` Po Lu
2022-09-19 14:20 ` Eli Zaretskii
2022-09-19 14:54 ` Gregory Heytings
2022-09-19 15:51 ` Eli Zaretskii
2022-09-19 16:02 ` Gregory Heytings
2022-09-19 16:14 ` Eli Zaretskii
2022-09-19 16:30 ` Gregory Heytings
2022-09-19 13:37 ` Gerd Möllmann
2022-09-19 13:46 ` Stefan Monnier
2022-09-19 12:33 ` Gregory Heytings
2022-09-19 10:14 ` Gregory Heytings
2022-09-19 10:17 ` Lars Ingebrigtsen
2022-09-19 11:29 ` Gregory Heytings
2022-09-19 12:23 ` Po Lu
2022-09-19 19:51 ` Gregory Heytings
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=87leqfrelm.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.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).