[GRASS-dev] g.extension: still fetching from SVN?

Ken Mankoff mankoff at gmail.com
Mon Aug 5 13:41:34 PDT 2019


On 2019-08-05 at 16:26 -04, Martin Landa <landa.martin at gmail.com> wrote...
> Hi,
>
> po 5. 8. 2019 v 22:22 odesílatel Markus Neteler <neteler at osgeo.org> napsal:
>> https://trac.osgeo.org/grass/milestone/7.6.2
>> -> 5th Aug 2019 was planned :-)
>
> yes, there is one blocker issue which should be solved before any
> release. How to deal with svn keyword propagation in the code ($DATE$,
> $REVISION$, ...). There is no straightforward replacement for git to
> my knowledge. Any suggestion very welcome!

It seems like this is not officially supported, can be done easily with some scripts [1], but is not recommended [2].

Why is it needed?

I regularly use the gitinfo LaTeX package that provides a git commit hook. This hook simply puts latest hash (and some other commit data such as author, branch, date, etc.) into a file, that the LaTeX package then uses to make nice headers or footers with the commit info.

Could a commit hook make a file that is then somehow included in the footer of each HTML file?

  -k.

[1] https://stackoverflow.com/questions/11534655/git-keyword-substitution-like-those-in-subversion
[2] https://git.wiki.kernel.org/index.php/GitFaq#Does_Git_have_keyword_expansion.3F


More information about the grass-dev mailing list