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

RE: Move from CVSNT to SVN?

From: Bob Archer <bob.archer_at_amsi.com>
Date: Thu, 10 Sep 2009 12:17:58 -0400

> > 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.
> Hmmm ... not sure I understand this concept entirely. I basically use
> a CVS
> tag every time I do a build or a release to "mark" the version of all
> files
> required for that particular build. 99% of the time, this tag is a one
> time
> thing. However, it does happen every-so-often that a build fails b/c
> someone forgot to check in a file. So instead of giving it a new build
> number once the file is committed, I just retag with the same tag name
> and
> perform the build. Would that concept/workflow cause problems in SVN?

No, it won't be a problem. Just delete the tag and re-create it. We do this also.

> Secondly, I'm a bit confused with the concept of version numbers in svn
> overall. I understand that a version relates to the state of the
> overall
> project - not any individual file as in CVS. So if I am working in a
> specific file, and want to see a previous version of that file, does
> that
> require the client to download the entire code repository of a previous
> version? In CVS, since files are versioned independently, I can easily
> see
> the state of any one file throughout its history, and retreive a
> particular
> revision for that one file and stick with it (ie: sticky tags). Does
> that
> concept still hold true for svn?

Yes, a WC can have "mixed revisions" so you can "update" a specific folder to a certain revisions. Generally you want everything to be at the HEAD (most recent) revision, but you can update a path or a single file to a previous rev number. Also, svn will keep you from committing changes to it since it will recognize that it is older than the HEAD revision. There are also tools to diff what is in your working copy with a previous revision of the file.

The main difference is that a file could be the same in several revisions. But, that is just semantics and doesn't really affect anything.

> Another problem I had read about a while back was with file renaming; I
> had
> understood it not to be fully functional. Is that the case, or was I
> misinterpreting information?

You can "rename" files but internally it is a delete and then an add. But, subversion is smart enough to keep ancestry in tact. The confusion comes when you rename say "filea" to "fileb" then create a new "fileb". That can make svn loose it's mind abit.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-10 18:18:44 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.