all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70966@debbugs.gnu.org, monnier@iro.umontreal.ca, steven@stebalien.com
Subject: bug#70966: 30.0.50; eshell/diff produces track-changes errors
Date: Sat, 25 May 2024 23:25:47 -0700	[thread overview]
Message-ID: <m2zfsdnl78.fsf@newartisans.com> (raw)
In-Reply-To: <86wmniz5pc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 May 2024 10:55:11 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

> Ping!  How should we go about resolving this issue?

Sadly, I no longer have the original Git history for Eshell, and these lines
were present when it was brought into Emacs core. I think the only thing you
can assume is that I made a mistake and the fix presented here is the correct
one, and then perhaps it may become manifest later why I made that decision
long ago.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2





  reply	other threads:[~2024-05-26  6:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 18:05 bug#70966: 30.0.50; eshell/diff produces track-changes errors Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 18:30 ` Eli Zaretskii
2024-05-16 15:58   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 16:15     ` John Wiegley
2024-05-25  7:55       ` Eli Zaretskii
2024-05-26  6:25         ` John Wiegley [this message]
2024-05-26  8:16           ` Eli Zaretskii
2024-05-28 21:42             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-28 23:48               ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=m2zfsdnl78.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=70966@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=steven@stebalien.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.