From: Eli Zaretskii <eliz@gnu.org>
To: Ali Bahrami <ali_gnu2@emvision.com>
Cc: emacs-devel@gnu.org, schwab@linux-m68k.org,
stefankangas@gmail.com, rms@gnu.org
Subject: Re: Finding the dump (redux)
Date: Mon, 19 Apr 2021 18:58:03 +0300 [thread overview]
Message-ID: <83eef6s1v8.fsf@gnu.org> (raw)
In-Reply-To: <1bf535b8-ca77-0eb6-9ac3-029b686b3671@emvision.com> (message from Ali Bahrami on Mon, 19 Apr 2021 09:41:17 -0600)
> Cc: schwab@linux-m68k.org, rms@gnu.org, emacs-devel@gnu.org
> From: Ali Bahrami <ali_gnu2@emvision.com>
> Date: Mon, 19 Apr 2021 09:41:17 -0600
>
> It would also really help with that manifest problem.
> Perhaps it is "paradise lost", but "paradise lost on
> source change" would be a big upgrade.
The "paradise lost" I alluded to is that with native-compilation, when
you modify Emacs and rebuild, some of the hashes in the *.eln files'
names could legitimately change, and thus cause you to update the
manifest.
next prev parent reply other threads:[~2021-04-19 15:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 19:38 Finding the dump (redux) Ali Bahrami
2021-04-17 18:45 ` Eli Zaretskii
2021-04-18 0:15 ` Ali Bahrami
2021-04-18 7:55 ` Eli Zaretskii
2021-04-18 8:18 ` Andreas Schwab
2021-04-18 16:05 ` Glenn Morris
2021-04-19 4:53 ` Richard Stallman
2021-04-19 8:35 ` Andreas Schwab
2021-04-19 13:00 ` Eli Zaretskii
2021-04-19 13:04 ` Ali Bahrami
2021-04-19 13:14 ` Eli Zaretskii
2021-04-19 13:34 ` Stefan Kangas
2021-04-19 14:39 ` Eli Zaretskii
2021-04-19 15:41 ` Ali Bahrami
2021-04-19 15:58 ` Eli Zaretskii [this message]
2021-04-19 16:08 ` Ali Bahrami
2021-04-19 17:09 ` Eli Zaretskii
2021-04-19 4:01 ` Ali Bahrami
2021-04-19 13:26 ` Stefan Monnier
2021-04-19 14:28 ` Eli Zaretskii
2021-04-19 14:50 ` Stefan Monnier
2021-04-19 15:43 ` Ali Bahrami
2021-04-19 16:06 ` Eli Zaretskii
2021-04-19 16:39 ` Ali Bahrami
2021-04-19 17:19 ` Eli Zaretskii
2021-04-19 18:03 ` Ali Bahrami
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=83eef6s1v8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ali_gnu2@emvision.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stefankangas@gmail.com \
/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.