[Phpwiki-talk] cvs log tag

[Steve W. <sw...@pa...>]

I'm thinking of adding a block to the bottoms of all files in the form:

<?
// $Log$
?>

What this would do is include the cvs log message every time a file is
committed. I've found from work in the Real World that when a project is
moved to a new cvs server, all the messages are lost.

To make this even more pertinent would be: for each file in PhpWiki, add
the block, plus all cvs messages for that file to date. This could be done
by me by hand, over time, or perhaps there is a way to do this
programmatically (probably a convoluted one-off Perl script).

If anyone objects please let me know. Below is a much longer explanation
from the red bean cvs book.

~swain




$Log$        ==>  accumulating log messages for the file, expands to ==>
$Log: hello.c,v $
Revision 1.2  1999/07/26 06:47:52  jrandom
...and this is the second log message.

Revision 1.1  1999/07/26 06:39:46  jrandom
This is the first log message...

The $Log$ keyword is the only one of these that expands to cover multiple
lines, so its behavior is unique. Unlike the others, it does not replace
the old expansion with the new one, but instead inserts the latest
expansion, plus an additional blank line, right after the keyword (thereby
pushing any previous expansions downward). Furthermore, any text between
the beginning of the line and $Log is used as a prefix for the expansions
(this is done to ensure that the log messages stay commented in program
code). For example, if you put this into the file

// $Log$

it will expand to something like this on the first commit:

// $Log: hello.c,v $
// Revision 1.14  1999/07/26 07:03:20  jrandom
// this is the first log message...
//

this on the second:

// $Log: hello.c,v $
// Revision 1.15  1999/07/26 07:04:40  jrandom
// ...and this is the second log message...
//
// Revision 1.14  1999/07/26 07:03:20  jrandom
// this is the first log message...
//

and so on:

// $Log: hello.c,v $
// Revision 1.16  1999/07/26 07:05:34  jrandom
// ...and this is the third!
//
// Revision 1.15  1999/07/26 07:04:40  jrandom
// ...and this is the second log message...
//
// Revision 1.14  1999/07/26 07:03:20  jrandom
// this is the first log message...
//

You may not want to keep your entire log history in the file all the time;
if you do, you can always remove the older sections when it starts to get
too lengthy. It's certainly more convenient than running cvs log, and it
may be worthwhile in projects where people must constantly read over the
logs.