Leon Zandman schrieb:
> 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 ;-)
Well, yes, that's true, when you take a look onto functionallities like
"atomic commits" or the very efficient database backend. (those two were
the reason why subversion is on the list of possible tools)
>> 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).
The file just get's copied to one location, to get a environment where
it can be compiled and tested. It's like when you want to test a new
version of a pc program- you "copy" it from a location to your pc and
test it. when you develop someting in the program, this has nothing to
do with your windows or linux, just with the program.
Received on Mon Apr 24 20:05:52 2006