next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects
On Fri, 29 Oct 1999, Bob Adams wrote:
> Does either of you know off hand how I can change this code to display
> Atlantic time.
If we pass "-zLT" to all of the rcs checkout commands, a date of (UTC)
1990/01/12 04:00:00 would show up instead as 1990/01/12 01:00:00-03.
If it weren't for the "-03" I'd just go ahead and do it, but I think it
might just be more confusing than it's worth.
> Also, is there a day-of-week $ code?
No, I think $Date$ is the only date keyword. According to the manpage for
co(1), these are the available keywords:
$Author$
The login name of the user who checked in the revision.
$Date$
The date and time the revision was checked in. With
-zzone a numeric time zone offset is appended; other-
wise, the date is UTC.
$Header$
A standard header containing the full pathname of the
RCS file, the revision number, the date and time, the
author, the state, and the locker (if locked). With
-zzone a numeric time zone offset is appended to the
date; otherwise, the date is UTC.
$Id$ Same as $Header$, except that the RCS filename is
without a path.
$Locker$
The login name of the user who locked the revision
(empty if not locked).
$Log$
The log message supplied during checkin, preceded by a
header containing the RCS filename, the revision
number, the author, and the date and time. With -zzone
a numeric time zone offset is appended; otherwise, the
date is UTC. Existing log messages are not replaced.
Instead, the new log message is inserted after
$Log:...$. This is useful for accumulating a complete
change log in a source file.
Each inserted line is prefixed by the string that pre-
fixes the $Log$ line. For example, if the $Log$ line
is // $Log:tan.cc $ , RCS prefixes each line of the
log with " " """ .}S 1 3 " // ." " " " "" "" "" "" ""
"" This is useful for languages with comments that go
to the end of the line. The convention for other
languages is to use a * prefix inside a multiline com-
ment. For example, the initial log comment of a C pro-
gram conventionally is of the following form:
/*
* $Log$
*/
For backwards compatibility with older versions of RCS,
if the log prefix is /* or (* surrounded by optional
white space, inserted log lines contain a space instead
of / or (; however, this usage is obsolescent and
should not be relied on.
$Name$
The symbolic name used to check out the revision, if
any. For example, co -rJoe generates $Name: Joe $.
Plain co generates just $Name: $.
$RCSfile$
The name of the RCS file without a path.
$Revision$
The revision number assigned to the revision.
$Source$
The full pathname of the RCS file.
$State$
The state assigned to the revision with the -s option
of rcs(1) or ci(1).
The following characters in keyword values are represented
by escape sequences to keep keyword strings well-formed.
char escape sequence
tab \t
newline \n
space \040
$ \044
\ \\
Hmmm, we're killing RCS so I guess this is all irrelevant for IPs :)
Could be useful for the directories where we'll be keeping RCS.
The $Log$ code would work in HTML like:
<!-- Changelog:
$Log$
-->
next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects