Jump to content

source code macros


nawglan

Recommended Posts

Kinda, except, in cvs it actually modifies the file so that if you export that file it has the expanded string.

 

eg:

  The following is a commonly used file header:

#
# Author   : Name <email@address>
# Subject  : Title of Documentation
# Revision : $Id$
#
When exported from CVS, the above file header will expand out to something like:

 

#
#  Author   : Name  <email@address>
#  Subject  : Title of Documentation
#  Revision : $Id: File2.java,v 1.3 2004/06/02 17:30:42 JHunter Exp $
#

 

So, if the client reports a bug on the code, they can also tell us what revision of the file they have.  This helps us identify a starting point to see where the bug was introduced.

 

The client doesn't have Plastic SCM installed, so attributes and doing queries doesn't help.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...