From: 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 03:44:45 -0500 [thread overview]
Message-ID: <CANCp2gYp5xhndOT7vNOqaNmmN50qzQ5NV0Uvi9i4pRhDXqHMuQ@mail.gmail.com> (raw)
In-Reply-To: <83fu81luke.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Sat, Dec 23, 2017 at 3:25 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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.
>
Path names give you good places to start looking for the file.
And often they can quickly give information as to what's up, e.g. I am
running from the stable or development branch. Or running from an Ubuntu
build or a source-code build.
[-- Attachment #2: Type: text/html, Size: 1813 bytes --]
next prev parent reply other threads:[~2017-12-23 8:44 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
2017-12-23 8:44 ` Rocky Bernstein [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANCp2gYp5xhndOT7vNOqaNmmN50qzQ5NV0Uvi9i4pRhDXqHMuQ@mail.gmail.com \
--to=rocky@gnu.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 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.