2009/1/8 SVNUser <anild_at_vertexcs.com>:
> Hi:
>
> We are using Tortoise SVN Tool for our project for the first time. We feel
> that it is a great tool for Configuration Management.
>
> Earlier, We are using VSS (Microsoft Visual Source Safe)
>
> There is one issue reg. revisions in Tortoise SVN:-
>
> In VSS, for each file, versions/revisions are auto-incremented i.e. if we
> add a file, it will take as Version 1; if we modify that file and update to
> VSS, version number is changed to 2 and so on and similar for other files.
>
> Where as in Tortoise SVN, We have observed that each commit is treated as
> one change to the repository and has a global revision number.
>
> An activity (add/modify/delete) on any file is treated as a revision
>
> (Eg: I have added a file x to the svn repository - treated as Revision 1.
> Added a file y to the svn repository - treated as Revision
> 2.
> Modified x and commited to the svn repository - treated as Revision 3.
> Modified y and commited to the svn repository - treated as Revision 4.
> Deleted y and commited to the svn repository - treated as Revision 5 and
> so on...)
>
>
> Are there any means / options to change this pattern - i.e. Revision
> numbers on a file or entry in the repository should be per-file and not
> per-commit basis?
No. That is the way subversion works. Revision numbers are an internal
reference which happens to be exposed for convenience. Just because
VSS does it that way doesn't mean it is the only correct way. If you
absolutely must use per-file revisions you will have to use something
different.
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
Received on 2009-01-08 15:06:43 CET