On Tue, 2008-12-02 at 19:40 +0530, nishant saxena wrote: > Hi, > I am Nishant, working in LAMP and have good knowlege of CVS. I am facing a > problem, > In CVS we had Tagging systems where we use to have unique tags on single > file(s), no matter where the file is, or how many revisions are present over > it, by using TAG on can pull all the files in one shot and reduce the pain > in different releases going on same file(s), deployment of release, > reverting back to one release and many more. > > But now i am using SVN, now here i know that we had somthing called TAG but > the concept and the way this has been inplemented is different what we had > in CVS. > > Can you please let me know, is there any way or technique which is same as > CVS coz i didnt get answers for the follwoing questions > > 1. In CVS we can create working and base brachs and the development can go > on working branch. > 2. In CVS under working brach we had same one file(s) and one can use the > TAG techique to pull out the files and work can go on. > 3. In CVS one can at any moment take the files associated in a release. for > eg. > > > Release TAG date > > Rel1 R1 > 1-12-08 > > Rel2 R2 > 6-12-08 > > Rel3 R3 > 20-12-08 > > and all these releases are merged in main branch > > now if on 25-12-08 i required Rel1 to be pushed again then in CVS if i > checkout files using R1 i could get all the files from CVS this reduce the > tension to maintain any doc or remember the files in a release and can > revert back to any changes but, in SVN how one can achive this kind of > thing. > > -- > nishant
Hi Nishant, Here is the problem, The SVN developers assert with pride that they have got rid of 3 measurements by working with tags and branches. In practice it means that they have substituted both concepts for a capability of copying file(s) or directories within the repository with saving the history of changes. That is, both tag creation and branch creation are substituted for copying within the repository. From the SVN developers' viewpoint, this is very elegant decision, which simplifies one's life. However, we think that there is nothing to be proud of. As for branches, everything is not so bad, now branches are nothing but separate folders in the repository, which earlier have had some interconnection. As for tags, everything is much worse. Now you cannot tag a code, this function is simply missing. Certainly, to some extent this is compensated by universal numbering of files in SVN, that is, the whole repository gets the version number, but not each separate file. However, I suppose you will not deny that it is not very convenient to store a four- digit number instead of a symbolic tag. So thats the reason they put some best practices. http://svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html The way SVN does it is here. http://research.mosuma.com/faq/howto/svn_branch_merge Hope this helps. Best Regards Sumit Upadhyay
