[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

OEBS $Id$ compatible format

From: Andrej A. Nagornykh <a.nagornykh_at_borlas.ru>
Date: 2006-10-25 09:21:21 CEST

Hello

Please, give me the way to integrate standard SVN $Id$ future with standard OEBS RCS information witch looks like this:
$Header: apiinces.pls 115.20 2003/04/03 17:37:35 ajmcguir ship $

($Header: FileName CompositRevision DateTime LastModifiedBy $)

Essentially, that Revision number looks like composite field:

<release>.<Revision>[.<branch>.branch version] where
release is an integer defined for the source control area (115,118,120), for example
Revision is an integer between 0 to infinite (it is good revision of last modification)
branch is an integer
branch version is an integer between 0 and infinite

At least required:
<release>.<Revision>

Please, provide me information about any official way to get this feature/decision for Oracle corp.

Best regards,
Andrey Nagornykh
Senior Developer
Borlas IBC
(Oracle CIS Russian Federal Treasury Project)

 
Received on Wed Oct 25 10:48:52 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.