[petsc-dev] dates of last change on PETSc web pages

[Sean Farley]

>
> I thought that when someone committed one of these files, as part of the
> commit process hg would stick the current data into that file. If that is
> not possible then a trigger when pushing something to the master repository
> with a change in the file the trigger would put the date into the file
> (perhaps creating another entry in the commit history at that time).
>
>   RCS has this support trivially and for a ton of decades.
>
> Demo program for RCS
>   // $Author: ola $
>   // $Date: 1997/01/20 22:58:41 $
>   // $Id: foo.cc,v 1.1 1997/01/20 22:58:41 ola Exp $
>
>
> http://mercurial.selenic.com/wiki/KeywordExtension  seems to be what we
> should use. It appears that the hg makes sure the working copy always has
> the value (Date of last change in our case) in files one sees.
>
>  Check it out.


Ok, I was totally misunderstanding what was going on. There are some ways
to do that I've seen on the mercurial list. I think you're right about the
keyword extension being what we want but I'll have to check it out in depth
more. Sorry about the confusion.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120320/435d4a2e/attachment.html>