All geek questions in one place

Subversion and mixed versions: a recipe for broken assemblies?

I am only returning to subversive activities after using TFS for some time, and in general I quite go out :)

There is one thing that I remember differently. I do not remember that I could make an obsolete working copy. Or maybe my memory just brings me to the definition of "obsolete." I thought “obsolete” means that any file has been affected since the last update of my working copy, and not just that the file that I touched locally was affected (what I would call a conflict).

The reason I see this as a problem is because it’s very easy to “break the assembly” if I can make my changes without first integrating them with the changes made by others.

So was this mixed version added, or is it just me?

+3
source share
5 answers

This is you, because it has always been like this :-)

Your commit will fail if any of the elements that you are trying to commit are outdated, and the repository has one “common” version number, but for now, everything you are going to accomplish, for today, you CAN commit. Of course, this does not mean that it is best practice.

, svn . , , , .

, , AFAIK TFS , ?

+3

: , , , , . , .

, .

: , , , , , (). . , .

, . /release _4.2.0, , - ( "branch/release_4.2.1" ) . , , , "tags/release_4.2.1". , , .

+1

​​ "" . VCS, , , VCS , . .

Subversion , CVS. , - . , Git ( TFS), . - , . , - , , , .

+1

, , . , , , . , , . , , , .

, Tortoise: http://tortoisesvn.net/node/13

"Now, if you change File2 and try to commit it, it tells the repository that File2 is in revision 2 with local changes, but the repository is already in revision 3. If you then upgrade, File2 will also be in revision 3 (and, Of course, your local changes will still be present).

I really do not get the message "deprecated", but you should think that it would be at some point?

0
source

Source: https://habr.com/ru/post/1715213/

More articles:


All Articles