From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, Gregor Zattler <telegraph@gmx.net>,
55969@debbugs.gnu.org
Subject: bug#55969: Feature request: configure option to build Emacs without any documentation
Date: Wed, 15 Jun 2022 14:50:41 +0200 [thread overview]
Message-ID: <87edzqytsu.fsf@gmail.com> (raw)
In-Reply-To: <877d5ihzq9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 15 Jun 2022 14:34:38 +0200")
>>>>> On Wed, 15 Jun 2022 14:34:38 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Glenn Morris <rgm@gnu.org> writes:
>> You don't need a configure option; just use
>>
>> make -C src emacs
>>
>> (used to work; haven't checked recently)
Lars> Yes, I don't think a configuration option here will give us
Lars> something substantially easier to work with during bisection.
Lars> However, it might be nice to have a target in GNUmakefile for doing
Lars> bisection that would allow you to say
Lars> git checkout ...; git clean -dfx; make without-manuals
Lars> that would run autogen/configure as normal, but then "make -C src emacs"
Lars> instead of "make all"?
If this is for the purposes of historical bisection, then you'd need a
time machine to install those changes. 'git bisect' can take a script
to determine good/bad, so you'd just stick the appropriate commands in
there.
Robert
--
next prev parent reply other threads:[~2022-06-15 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YpuV9DKe9kzNt5np@ACM>
[not found] ` <87o7z61v59.fsf@gmail.com>
[not found] ` <Yp3l+rjJ0mAIcVZJ@ACM>
[not found] ` <87bkv527p5.fsf@gmail.com>
[not found] ` <835yld93w7.fsf@gnu.org>
[not found] ` <877d5t0yrn.fsf@gmail.com>
[not found] ` <Yp92eI2pEuc/gQu4@ACM>
[not found] ` <jwvtu8wbbjb.fsf-monnier+emacs@gnu.org>
[not found] ` <87r140yuof.fsf@gmail.com>
[not found] ` <E1nzQh5-0001OB-22@fencepost.gnu.org>
[not found] ` <875yl9e7zm.fsf@gmail.com>
[not found] ` <83czfh12kp.fsf@gnu.org>
[not found] ` <87pmjhghu2.fsf@localhost>
[not found] ` <835yl910gp.fsf@gnu.org>
[not found] ` <87wndndbhq.fsf@gmail.com>
[not found] ` <83bkuzznws.fsf@gnu.org>
[not found] ` <877d5mqmkh.fsf@localhost>
[not found] ` <E1o0sgC-0000jg-U3@fencepost.gnu.org>
[not found] ` <83k09kt1uk.fsf@gnu.org>
[not found] ` <87v8t4klox.fsf@localhost>
[not found] ` <83h74ntsix.fsf@gnu.org>
2022-06-14 13:08 ` bug#55969: Feature request: configure option to build Emacs without any documentation Gregor Zattler
2022-06-14 13:36 ` Eli Zaretskii
2022-06-14 17:52 ` Glenn Morris
2022-06-15 12:34 ` Lars Ingebrigtsen
2022-06-15 12:50 ` Robert Pluim [this message]
2022-06-15 16:39 ` Lars Ingebrigtsen
2022-06-15 17:23 ` Lars Ingebrigtsen
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=87edzqytsu.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=55969@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@gnu.org \
--cc=telegraph@gmx.net \
/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).