For better or worse, I am using rcs to track changes to HTML and JSON files exported from chatGPT. Some of these contain chats with embedded $keyword$'s. These get expanded on ci check in. How do I disble this without stepping on these files?

Sometimes I see dates enclosed in between two $ (dollar) signs, eg. $Date: 2018/11/11 10:05:10 $ or $Date: Tuesday 06 April 2004 - 14:10:05$. I've seen this mostly on personal homepages, most probably written in some markup language and then exported to HTML, and once in a PDF document. The HTML source code did not have any relevant meta tag (such as generator) and websearch is not very good when it comes to special characters, so... My question is which software produces this output.

Is there an RCS command similar to git status, svn status, and cvs status that can show the status of each file within a directory? For example, if a file has been modified since the last check-in, such a command should say that the file is "modified". In addition, it should show whether or not the file is locked (and locked by whom).

Suppose a file has 4 revisions (1.1 to 1.4). I deleted revisions 1.2 and 1.3 using rcs -o1.2:1.3 myfile.txt. Now I want to change revision number 1.4 to become revision number 1.2. How do I do this using RCS?

The freedesktop.org media type database shared-mime-info has [a filename pattern *,v](https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/b969e1c74e7c905a96c1590f5350a264dbaa83ae/data/freedesktop.org.xml.in#L5854) associated with MIME type text/plain, and I can't figure out why - if only because ,v and *,v are basically useless as search terms! [The 2008 commit that added the pattern](https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/bf4994fb0b4d15f227be0f71f6f22322fc53897f) doesn’t explain it, though the test case does point to [a bug on RedHat’s Bugzilla](https://bugzilla.redhat.com/show_bug.cgi?id=430203) . There, someone had “RCS files” with filenames ending in ,v, and the bug was that they were being recognised as audio files. Without further context, I can only guess that “RCS files” refers to Revision Control System, rather than radar cross-section data or Autodesk ReCap scan files… Why did this one user’s weird experience lead to a change in shared-mime-info for everyone? Was it a widespread problem, perhaps because RCS was known to generate files with that ending? Why was adding it to shared-mime-info an appropriate response† to the bug, rather than (say) finding out why these random files were being treated as audio? ---- † I say “response”, not “fix”, because it’s not clear to me that it *did* fix the user’s problem. The bug was closed because it ceased to occur in later versions of the software, which isn’t explicitly credited to the change in shared-mime-info.

I have installed RCS in Ubuntu 20.04 using sudo apt-get install rcs. The usual RCS commands such as ci, co, rlog, rcsdiff, rcsclean, etc. work as expected. However, rcsfreeze is missing. When I try to run rcsfreeze, I get rcsfreeze: command not found. Why is it missing? How do I get the rcsfreeze command?

I have a machine running Ubuntu 6.06. Source files under rcs (no git available). I need to visually compare older revs of files with the checked out version. Until now I have moved the file and compared. mv test.c tmptest.c co -r1.16 test.c xxdiff test.c tmptest.c mv tmptest.c test.c I know I can make this in a script, but is there a better way to do this? Without touching test.c?

I have multiple project trees of legacy code that are using RCS for version control with multiple users. I'd like to be able to walk the tree and test if any files are checked out (and thus the tree is not ready to be packaged for distribution update). For example, I have a test tree: tree -p . . ├── [-r--r--r--] file1 ├── [drwxrwxr-x] RCS │   └── [-r--r--r--] file1,v ├── [drwxrwxr-x] subdir1 │   ├── [drwxrwxr-x] RCS │   │   └── [-r--r--r--] sfile1,v │   └── [-rw-r--r--] sfile1 └── [drwxrwxr-x] subdir2 ├── [drwxrwxr-x] RCS │   └── [-r--r--r--] sfile2,v └── [-r--r--r--] sfile2 5 directories, 6 files In which all files but sfile1 are checked in to their respective RCS dirs. sfile1 has been checked out and modified. rlog subdir1/sfile1 (a file that is properly checked-out) returns: RCS file: subdir1/RCS/sfile1,v Working file: subdir1/sfile1 head: 1.1 branch: locks: strict torfey: 1.1 access list: symbolic names: keyword substitution: kv total revisions: 1; selected revisions: 1 description: ---------------------------- revision 1.1 locked by: torfey; date: 2016/07/20 13:09:34; author: torfey; state: Exp; Initial revision ============================================================================= Whereas rlog subdir2/sfile2 (a file that is properly checked-in) returns: RCS file: subdir2/RCS/sfile2,v Working file: subdir2/sfile2 head: 1.1 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 1; selected revisions: 1 description: ---------------------------- revision 1.1 date: 2016/07/20 13:10:04; author: torfey; state: Exp; Initial revision ============================================================================= So the command I'd like would, given a directory argument, search for all files under that dir that are part of RCS and return names of any that are not checked in. (Ideally, also if there's some other state that is detectable and bad, like not locked yet different from checked in version, report that too.) test_rcs_tree . It would return, for my above simple case: ./subdir1/sfile1 checked-out What I'm struggling with is whether there's maybe something out there that already does this that I'm just missing in all my searches. I'm running on RHEL 6.7 which has rcs 5.7, gnu awk 3.1.7, gnu make 3.81, bash 4.1.2