From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs is not reproducible
Date: Sat, 22 May 2021 23:31:50 -0400 [thread overview]
Message-ID: <jwvo8d22kmb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <jwvk0nxs4er.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 17 May 2021 12:40:39 -0400")
>> Is there currently any work underway to make Emacs reproducible?
> There has been changes made in the past to fix some problems.
> I have a pending patch in bug#46502 (see below) which aims to fix some
> more of those problems, but still haven't heard confirmation that it
> helps.
This is quite odd: both in bug#46502 and here again I don't hear
anything back from my proposal (not even some complaint that it doesn't
apply or it breaks something), even tho all I'm asking if for someone to
try and confirm whether it makes the build more (or less?) reproducible,
which I thought should be reasonably easy to do.
What am I missing?
Stefan
next prev parent reply other threads:[~2021-05-23 3:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:28 Emacs is not reproducible Bone Baboon
2021-05-17 15:45 ` Alan Mackenzie
2021-05-17 15:55 ` Achim Gratz
2021-05-17 15:54 ` Eli Zaretskii
2021-05-17 16:40 ` Stefan Monnier
2021-05-23 3:31 ` Stefan Monnier [this message]
2021-05-23 23:52 ` Glenn Morris
2021-05-25 17:41 ` Stefan Monnier
2021-05-25 17:52 ` T.V Raman
2021-05-25 18:03 ` Glenn Morris
2021-05-26 20:58 ` Stefan Monnier
2021-05-27 12:24 ` Mattias Engdegård
2021-05-27 21:33 ` Stefan Monnier
2021-05-25 18:27 ` Basil L. Contovounesios
2021-05-27 21:32 ` Stefan Monnier
2021-05-28 9:00 ` Basil L. Contovounesios
2021-06-05 16:26 ` Warning in tramp.el (was: Emacs is not reproducible) Stefan Monnier
2021-06-06 6:42 ` Warning in tramp.el Michael Albinus
2021-06-06 17:48 ` Stefan Monnier
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=jwvo8d22kmb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bone.baboon@disroot.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).