From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 75398@debbugs.gnu.org
Subject: bug#75398: 30.0.93; files.el documentation refers to "ITS-id" version control
Date: Tue, 07 Jan 2025 00:10:43 -0500 [thread overview]
Message-ID: <E1tV1rX-0005dC-9a@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkm=xBS2dg_oztNKvJNEsqfPNnPSFKa+SpSAAKjXwKUrPyg@mail.gmail.com> (message from Stefan Kangas on Mon, 6 Jan 2025 09:46:02 +0000)
[[[ 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. ]]]
> I understand that "version control" refers to backup files rather than
> VCS, but what is "ITS-id"? I can't find any references to that in the
> manual, or by grepping, but since the text was written in 1993, is it
> possible that it refers to "Incompatible Time-Sharing System"...?
It might. Some of this code may have been translated from TECO in
1984/5. But I can't recall what it that term might refer to.
On ITS, the only place to store a version number was (1) in the second
filename or (2) in the file contents. When that text was written, was
there code in Emacs to store a version number in one of those places?
--
Dr Richard Stallman (https://stallman.org)
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:[~2025-01-07 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 9:46 bug#75398: 30.0.93; files.el documentation refers to "ITS-id" version control Stefan Kangas
2025-01-06 14:34 ` Eli Zaretskii
2025-01-06 17:15 ` Stefan Kangas
2025-01-06 18:31 ` Eli Zaretskii
2025-01-07 5:23 ` Stefan Kangas
2025-01-07 5:10 ` Richard Stallman [this message]
2025-01-07 12:27 ` Eli Zaretskii
2025-01-10 3:22 ` Richard Stallman
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=E1tV1rX-0005dC-9a@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=75398@debbugs.gnu.org \
--cc=stefankangas@gmail.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.