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

Re: Unclear: CVS and Subversion repository difference.

From: Marc Haisenko <haisenko_at_webport.de>
Date: 2005-06-17 09:57:18 CEST

On Friday 17 June 2005 01:46, Servico Tpd Rodrigo Alfonso Menezes Madera
> Well, since I am a programmer, I did what programmers do in such a case...
> I researched
> (after Google said he wouldnŽt comment on the subject) and made a handful
> of tests. The
> result only made my mind almost blow. I ran TortoiseSVN (I know, I know,
> IŽm only mentioning
> it on this list, not a problem in it whatsoever) and became even more
> confused: even though
> my ChessGame directory had release 5, the file DrawChessBoard.c++ had a
> release of 1, the
> "src" directory had a release 3, and you can imagine all this confusion
> that a goodŽol CVS
> user has to understand.

Just do "svn up" in both directories and all files will be at r5.

When you commit, a directory can then contain mixed revisions. Imagine the
following layout:

/foo/abc (r1)
/foo/bar (r1)

Some else edits and commit /foo/abc, which is now at r2. But in your directory
it's still at r1. You then edit /foo/bar and commit, and it will be at r3,
while your /foo/abc is still at r1. This is to reduce network traffic, AFAIK,
and to avoid surprises: imagine you commat /foo/bar and suddenly
your /foo/abc is different !

A simple "svn up" will fix this mixed revision issue.

> Please show me up some light. IŽm scared...

Don't be scared, you will soon see the light and never look back at CVS
again ;-)

> Thanks for your patience,
> Rodrigo


Marc Haisenko
Webport IT-Services GmbH
mailto: haisenko@webport.de
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 09:59:05 2005

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.