This custom git module seems to do add that kind of support. https://github.com/turon/git-rcs-keywords I haven't tested it - though it looks like it just needs to be added to the root directory of the repository and adjust some settings in gitconfig. Including this might add some overhead that we might want to avoid, though. On Wed, Jul 29, 2015 at 8:39 AM, Syd Bauman wrote:

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. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

The revision and timestamp data in the generated GLs comes from an "svn info" command that writes out an XML file that then gets pulled in by the XSLT. If you're using git, you can override the VCS=svn in the Makefile with a VCS=git, and then git is used to generate an equivalent XML file. So that should all still work fine. On Wed, Jul 29, 2015 at 12:27 PM, Martin Holmes wrote:

Personally I've always found the keywords extremely useful, and I do rely on them in other projects, but I don't recall anywhere in the processing where we use them. I think the rev number in the footer (and elsewhere) is inserted through the processing instruction <?insert revision?>.

Cheers, Martin

On 15-07-29 05:52 AM, Raffaele Viglianti wrote:

...

This custom git module seems to do add that kind of support. https://github.com/turon/git-rcs-keywords

I haven't tested it - though it looks like it just needs to be added to the root directory of the repository and adjust some settings in gitconfig.

Including this might add some overhead that we might want to avoid, though.

On Wed, Jul 29, 2015 at 8:39 AM, Syd Bauman wrote:

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. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived