Re: OEBS $Id$ compatible format

On 10/25/06, Andrej A. Nagornykh <a.nagornykh@borlas.ru> wrote:

> Please, give me the way to integrate standard SVN $Id$ future with standard
               ^^^^^^^^^^^^^^^^^^

1) get the sourcecode of TSVN from
http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk
3) learn C/C++
2) study the sourcecode
4) implement the feature
5) create a patch
6) send the patch to this list
7) hope your patch will get accepted
8) wait for the next release

> 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.

Search the docs for SubWCRev.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org