<html>#2330: include date of build and git hash in documentation
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Cactus</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>The simpler version is here: <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactus/pull-requests/93" rel="nofollow">https://bitbucket.org/cactuscode/cactus/pull-requests/93</a> with it one checkout git will generate a string like <code>$Id: 57702847595f9879e6d743a66c483770450e3e53 $</code> wherever <code>$Id$</code> was found. Before committing / computing diffs it filters out the bits between <code>$Id:</code> and <code>$</code> so that the file is not constantly changed (this is the same behaviour as svn).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2330/include-date-of-build-and-git-hash-in'>https://bitbucket.org/einsteintoolkit/tickets/issues/2330/include-date-of-build-and-git-hash-in</a></p>
</html>