From: Eli Zaretskii <eliz@gnu.org>
To: Rocky Bernstein <rocky@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: A couple of things that I think should be in byte bytecode meta comments
Date: Sat, 23 Dec 2017 10:25:37 +0200 [thread overview]
Message-ID: <83fu81luke.fsf@gnu.org> (raw)
In-Reply-To: <CANCp2gYqdCCYnXeDeke3tVTu+oghY4L91zvniMMzkGwD44xi9w@mail.gmail.com> (message from Rocky Bernstein on Fri, 22 Dec 2017 15:55:06 -0500)
> From: Rocky Bernstein <rocky@gnu.org>
> Date: Fri, 22 Dec 2017 15:55:06 -0500
> Cc: emacs-devel@gnu.org
>
> That there is also a SHA of the text. If the text in any of those 60 files is identical it doesn't matter for purposes
> of debugging and error location determination which one
> in the set you decide to call the source.
If there's a SHA, why do we also need a file name?
> I'm saying that the minuscule amount of times it will work will drown
> in the sea of times it won't. Worse, when it "doesn't work", it will
> many times produce a false alarm: the file name is different, but the
> contents was identical.
>
> If that's the case, then how is this different than what we have now?
If it isn't different, why add the recording of file names? It does
nothing to improve the situation.
next prev parent reply other threads:[~2017-12-23 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 17:54 A couple of things that I think should be in byte bytecode meta comments Rocky Bernstein
2017-12-22 17:55 ` Rocky Bernstein
2017-12-22 18:30 ` Eli Zaretskii
2017-12-22 18:49 ` Rocky Bernstein
2017-12-22 20:25 ` Eli Zaretskii
2017-12-22 20:55 ` Rocky Bernstein
2017-12-23 8:25 ` Eli Zaretskii [this message]
2017-12-23 8:44 ` Rocky Bernstein
2017-12-23 15:32 ` Robert Weiner
2017-12-23 17:16 ` Rocky Bernstein
2017-12-23 18:30 ` Robert Weiner
2017-12-24 2:44 ` Rocky Bernstein
2018-01-13 19:44 ` Thien-Thi Nguyen
2017-12-22 21:27 ` Andreas Schwab
2017-12-22 21:43 ` Rocky Bernstein
2017-12-23 8:25 ` Andreas Schwab
2017-12-23 8:35 ` Rocky Bernstein
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=83fu81luke.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rocky@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).