[p4] RCS keywords

Robert Cowham robert at vaccaperna.co.uk
Thu Nov 9 14:25:03 PST 2006

Fine but don't forget that change is when *that* file last changed (which
you can derive from its $Id$), rather than the last changelist for any file
in the project.

What I do for tools such as Vsstop4 scripts is to have keywords in the
changelog.txt file of which I do submit a new version for every "release".


> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of David Alban
> Sent: 09 November 2006 18:00
> To: perforce-user at perforce.com
> Subject: Re: [p4] RCS keywords
> Thanks for your response, David.
> What about simply including the keyword:
>   $Change$
> in my shell and perl tools?  That would at least let me 
> associate versions of files in the field back to their change list.
> I'd like to track the source version rather than a release version.
> These are in-house infrastructure tools.

More information about the perforce-user mailing list