Reason for text/plain pattern "*,v" in shared-mime-info?

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.