BlankDear all,
When new revisions/versions are delivered to be checked in in CVS, please=
be
sure to have the following php code in the script:
echo "<!-- \$Revision$ -->";
Why?
See the TaxAuthorityRates.php script.
When someone would like to report a bug, they are able to tell which CVS
revision the bug is found by checking the source in the browser.
When you checkout the script:
TaxAuthorityRates.php
You will see that CVS modified automticallly the code to:
echo "<!-- \$Revision: 1.1 $ -->";
When you display in the browser the source, you will see:
<!-- $Revision: 1.1 $ -->
I think this will save us lot's of time, because we are always sure or ar=
e
able to ask which revision we should use to be able to reproduce an
issue/bug.
I is also nice to be able to read which revision is installed in my own
runtime environment and to check when there is a newer revision available=
in
CVS.
May be we should consider some other cvs keywords too:
? $Name$=97Name of the sticky tag:
$Name: release_1_14 $
? $RCSfile$=97Name of the RCS file in the repository:
The header would be nice to include it in php comment. That saves bandwid=
ht.
$Header$=97Various pieces of information thought to be useful: full path =
to
the RCS file
in the repository, revision, date (in UTC), author, state, and locker.
(Lockers are rare,
although in the following example, qsmith has a lock.):
$Header: /usr/local/newrepos/myproj/hello.c,v 1.1 2001/06/01 03:21:13 \
random Exp qsmith $
I hope you all see these minor extra coding and use of CVS is valuable.
With best regards,
Dick Stins
|
