Good point. I don't know, but I bet our build process does look at that information to get, e.g., the revision number, etc., stuck at the bottom of each HTML page: TEI Guidelines Version 2.8.1a. Last updated on 29th June 2015, revision 13284. This page generated on 2015-07-02T21:54:21Z. I just quickly looked through the entire Stylesheets/ directory,[1] though, and did not find anything very suspicious. (All of the SVN keywords I found were attached to code that was dealing with sucking in a CSS file or uses "$Date" as an indication that "It's RCS". With one exception: the XPath functions tei:generateRevDate() and tei:tei:generateRevAuthor() look for the $LastChangedDate and $LastChangedBy Subversion keywords, respectively; which is weird, as the former keyword *always* appears as "$Date" in our source files, and the latter doesn't appear in our source files at all.) I, for one, quite like the keyword substitution capability. Does `git` not do that? If not, I presume there is some other mechanism to do this with `git`. (Parse the log message, perhaps? No option to output it in XML, though.)
It just occurred to me that GitHub won’t support svn:keywords such as $Date$ or $Rev$. Humans will probably adjust themselves but I don’t know whether any software piece in our (some) processing pipeline relies on this information?
Notes ----- [1] I looked for templates that matched comment() and attributes that contained the string $Id, $Date, $LastChangedDate, or $Rev.