From: Rocky Bernstein <rocky@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.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:35:04 -0500 [thread overview]
Message-ID: <CANCp2gbhBeTfxFxPEggMgTDEKkxhDjeSGuXpLAdr2iMtJpypmQ@mail.gmail.com> (raw)
In-Reply-To: <m2a7y9j1g3.fsf@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
It is clear from both email messages you haven't been paying attention as
this has been discussed before, same as in your other email.
(I'll admit though that there has been far too many grammar mistakes in
what I wrote.)
I'm not interested in carrying the discussion further. I've been through
these kind of discussions on the same topics a couple of times before. And
I know what the solution is should I want to pursue it.
On Sat, Dec 23, 2017 at 3:25 AM, Andreas Schwab <schwab@linux-m68k.org>
wrote:
> On Dez 22 2017, Rocky Bernstein <rocky@gnu.org> wrote:
>
> > Except when a project concatenates a bunch byecode files together. Also
> the
> > parent path information or lack of it can sometimes also be useful.
>
> That won't help if the files are moved.
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
[-- Attachment #2: Type: text/html, Size: 1539 bytes --]
prev parent reply other threads:[~2017-12-23 8:35 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
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 [this message]
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=CANCp2gbhBeTfxFxPEggMgTDEKkxhDjeSGuXpLAdr2iMtJpypmQ@mail.gmail.com \
--to=rocky@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).