svn - Does Subversion merge diff or just update revision on unmodified files -


We have some specialty branches that can be put on ice for a few weeks at a time. After making many changes in the trunk, it is best to merge the changes in the branches from the trunk or leave the branch and create a new branch directly from the trunk and copy the changes from the initial branch to it.

I ask for the merge, SVN only takes a separate trunk from the previous merge to the head and applies to that branch.

In many cases there is a huge increase in the changes in the trunk branch, so by the size of difference it will mean leaving a feature branch and creating a new with the change in facility branches.

This is an issue especially when many PDFs are up to date.

It seems that in another way for SVN, it feels like a file was never touched in the branch and therefore updates the amendment number, which, in its inherent difference, Instead of implementing indicates.

P> The output of subversion seems like it is implementing diffs.

It seems that another way for SVN will be to file a file in the branch Not touched and therefore the amendment number should be updated which indicates that it will be to avoid extra space for the difference.

AFAIK, there is no significant place in the dispute by implementing deformation. If the difference is small, then it should only take the same place as the amendment.

BTW merge into the branch from the trunk? It only makes sense when you later plan to merge the branch back into the trunk.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -