Hi,
I didn't fully understand your e-mail, but in general I think if things
can be done using CVS it should certainly be doable using SVN. Afterall
SVN is CVS on steroids ;-)
> 1. if a developer wants to make a change in a
> certain revision, he wants to do it into project_a
> and not into the trunk, but in fact the trunk
> revision should be updated.
If I understand correctly you want to make a change in a file that's
located in a branch, but you want the file's parent (or source copy) to
increase its revision number? That's weird. Revision numbers should only
increase if something has changed and in this case the file in trunk
didn't change, so its revision number also won't change. The global
revision number of the whole repository will increase, however. Each
commit will increase that global revision number (see the FAQ).
> 2. after creating a copy subversion stops to log
> the changes for the new revision, so log's are
> only backward, or do i misunderstand something ???
When you copy (branch) a file in Subversion it will be sort of
disconnected from its source copy in the trunk (or wherever you've
copied it from). If you query its log it will only show the history from
the moment it was copied. Also the log of the original file (in trunk)
will not show any entries from the copied file.
> 3. compared to CVS the handling of such a
> structure in subversion is more complicated (=user
> acceptance!!!) than in CVS.
I personally find SVN to be more user-friendly than CVS. The
command-line clients are much simpler to use. And TortoiseSVN (a Windows
SVN client) really rocks.
Greetz,
Leon Zandman
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 24 16:58:10 2006