nawglan Posted April 29, 2013 Report Share Posted April 29, 2013 In CVS, we could add this in the code: “$Id: $” and it would automatically timestamp the code. This was very helpful with our header comment blocks. Can Plastic SCM do something similar? Thanks. Link to comment Share on other sites More sharing options...
calbzam Posted May 2, 2013 Report Share Posted May 2, 2013 Hi, As far as I know these macro are similar that Plastic SCM attributes: http://www.plasticscm.com/features/user-defined-attributes.aspx Regards, Carlos Link to comment Share on other sites More sharing options...
nawglan Posted May 2, 2013 Author Report Share Posted May 2, 2013 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 More sharing options...
nawglan Posted May 3, 2013 Author Report Share Posted May 3, 2013 For those that come later, the following post helped and got me on the right track: http://www.plasticscm.net/index.php?/topic/385-rcs-style-keywords/ I'll post the code I write for this as a reply when it's completed. -- Dez. Link to comment Share on other sites More sharing options...
calbzam Posted May 3, 2013 Report Share Posted May 3, 2013 Thank you @nawglan!! Regards, Carlos Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.