Commit to SVN, preventing others from checking - is this possible?

I use SVN as a source control with ANKH and TortoiseSVN. I am writing huge changes to the project, and it takes several days to make changes, but nonetheless I still want to periodically back up. But if I complete other team members, they will be updated with my work in progress.

Is there a way I can “commit to backup” without changing the version (so that others will not be updated with my changes)?

Thank!

+3
source share
5 answers

. , Subversion.

+5

iconik's :

SVN branch. branch, , .

- , . , merge .

, , , ( ), , .

, SVN

+3

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

, Subversion. , git, mercurial bazaar, , . , , DVCS , . DVCS , , , Subversion. , , , .

+1

"" , . . , .. Subversion "".

http://svnbook.red-bean.com/en/1.1/ch05s02.html

"post" "pre" commit hooks / .

+1

, ( svn copy). , , , svn merge , , ( , ). , SVN -. devel (svn copy), -, , svn trunk (live), .

The advantage of this is to use one of the distributed repository systems, such as Mercurial (although this is a great product), that is, your branch is on a server that has more reliable hard drives and more frequent backups, If you commit your local Mercurial repository, and your desktop computer is dying, your work will be lost. It also means that if you want to collaborate with a selected group of people (I hope you have some kind of QA before you press the code on the trunk !!!), you can do this by pointing them to your branch.

0
source

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


All Articles