Andrey Repin wrote:
> Greetings, Les Mikesell!
>
>> You may need to adjust your workflow concepts a bit. In CVS, you would
>> normally use tags to tie a set of revisions together so you can
>> reproduce the state of a workspace - and in cvs tags are like labels
>> that you can float around. In subversion, tags are like snapshot
>> copies and normally are never revised so if your workflow depends on
>> floating a tag name so you can embed it in scripts you may have to
>> change a few things.
>
> I'd like to add that this concept of "floating tags" is what Subversion has in
> mind when you say "revision".
> Each revision consist of a complete, functional state of the project....
> ideally.
Yes, except you don't get to apply a well-known name to it. So it is hard to
embed the right revision number into an already written script... With CVS you
are generally forced to use tags because each file will have different revision
numbers and you need the tags as labels to identify the right revisions for a
set of files. With svn you can use tags but it is hard to re-use the same name
to identify a state that is ready for some processing step so you need to come
up with some extra workflow steps to pass a tag name or revision number around.
This may not be difficult but if you floated tags in CVS instead of making up
new ones for every change you may need to change your process with svn.
--
Les Mikesell
lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2393225
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-10 14:44:40 CEST