From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 51234@debbugs.gnu.org, Thomas Klausner <tk@giga.or.at>
Subject: bug#51234: emacs.pdmp file name (--fingerprint)
Date: Mon, 18 Oct 2021 15:13:53 +0200 [thread overview]
Message-ID: <871r4ijx0u.fsf@gnus.org> (raw)
In-Reply-To: <87y26q4srf.fsf@gmail.com> (Robert Pluim's message of "Mon, 18 Oct 2021 10:55:00 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> Lars> Yes, but it should be documented forever -- people will be wondering
> Lars> later, too.
>
> (info "(elisp) Building Emacs")
Yes, I guess...
Eli Zaretskii <eliz@gnu.org> writes:
> Me, I wonder how will those distros code with the *.eln files, which
> also include hashes that aren't known in advance. Solving the issue
> with the pdumper file will still leave this other one, with many more
> files.
>
> So perhaps the distros will just have to adapt?
That's a good point. So perhaps we shouldn't document how to get to a
known-name setup, because that won't work for nativecomp?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-18 13:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 7:07 bug#51234: emacs.pdmp file name (--fingerprint) Thomas Klausner
2021-10-16 13:43 ` Lars Ingebrigtsen
2021-10-18 7:41 ` Lars Ingebrigtsen
2021-10-18 8:01 ` Robert Pluim
2021-10-18 8:04 ` Lars Ingebrigtsen
2021-10-18 8:26 ` Robert Pluim
2021-10-18 8:46 ` Lars Ingebrigtsen
2021-10-18 8:55 ` Robert Pluim
2021-10-18 13:13 ` Lars Ingebrigtsen [this message]
2021-10-18 14:16 ` Eli Zaretskii
2021-10-19 20:42 ` Lars Ingebrigtsen
2021-10-18 12:31 ` Eli Zaretskii
2021-10-18 12:33 ` Thomas Klausner
2021-10-18 12:50 ` Robert Pluim
2021-10-18 13:08 ` Eli Zaretskii
2021-10-18 12:31 ` Eli Zaretskii
2021-10-18 13:43 ` Andreas Schwab
2021-10-18 18:09 ` Glenn Morris
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=871r4ijx0u.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51234@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=tk@giga.or.at \
/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.