From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: contovob@tcd.ie, mattiase@acm.org, 40725@debbugs.gnu.org,
schwab@linux-m68k.org, juri@linkov.net
Subject: bug#40725: 27.0.91; Tutorial reports false positive key rebindings
Date: Wed, 29 Apr 2020 22:32:35 -0400 [thread overview]
Message-ID: <E1jTz07-0001X5-U9@fencepost.gnu.org> (raw)
In-Reply-To: <83ees621fz.fsf@gnu.org> (message from Eli Zaretskii on Wed, 29 Apr 2020 10:30:56 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > The change history should record the rename. Then a human who sees a reference
> > to the old name can search for it and find out that the file was renamed.
> Not all modern VCSes record renames. Git doesn't.
If the change history won't do this automatically, the developers
should write it explicitly in some log entry. That won't be hard.
Also, it is useful to insert a file's previous names in a comment near
the start of the file.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-04-30 2:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 23:31 bug#40725: 27.0.91; Tutorial reports false positive key rebindings Basil L. Contovounesios
2020-04-20 14:28 ` Eli Zaretskii
2020-04-20 22:19 ` Basil L. Contovounesios
2020-04-21 13:39 ` Eli Zaretskii
2020-04-22 22:26 ` Basil L. Contovounesios
2020-04-23 14:33 ` Eli Zaretskii
2020-04-23 21:52 ` Juri Linkov
2020-04-24 6:55 ` Eli Zaretskii
2020-04-25 3:31 ` Richard Stallman
2020-04-25 8:54 ` Eli Zaretskii
2020-04-25 20:42 ` Juri Linkov
2020-08-18 13:54 ` Lars Ingebrigtsen
2020-08-18 18:52 ` Basil L. Contovounesios
2020-08-19 10:20 ` Lars Ingebrigtsen
2021-11-12 8:28 ` Lars Ingebrigtsen
2021-11-14 23:24 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-15 5:53 ` Lars Ingebrigtsen
2020-04-24 8:46 ` Mattias Engdegård
2020-04-24 10:20 ` Eli Zaretskii
2020-04-24 10:41 ` Mattias Engdegård
2020-04-24 11:21 ` Eli Zaretskii
2020-04-24 11:35 ` Mattias Engdegård
2020-04-24 12:13 ` Eli Zaretskii
2020-04-24 12:47 ` Mattias Engdegård
2020-04-24 13:32 ` Eli Zaretskii
2020-04-24 16:01 ` Mattias Engdegård
2020-04-25 3:33 ` Richard Stallman
2020-04-25 6:20 ` Eli Zaretskii
2020-04-27 2:18 ` Richard Stallman
2020-04-27 2:37 ` Eli Zaretskii
2020-04-27 6:11 ` Andreas Schwab
2020-04-28 2:49 ` Richard Stallman
2020-04-28 7:02 ` Andreas Schwab
2020-04-29 3:25 ` Richard Stallman
2020-04-29 7:30 ` Eli Zaretskii
2020-04-30 2:32 ` Richard Stallman [this message]
2020-04-24 19:48 ` Kévin Le Gouguec
2020-04-24 19:57 ` Eli Zaretskii
2020-04-24 15:38 ` Dmitry Gutov
2020-04-24 15:51 ` Eli Zaretskii
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=E1jTz07-0001X5-U9@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=40725@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=mattiase@acm.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).