All geek questions in one place

How can I save Subversion commit messages during merges?

Is there any Subversion that can create a commit message containing a list of all the commit messages used in the merge?

Our problem is that we tend to lose all the useful information about the history of changes that occur in the branches after they are combined. Usually, instead of a detailed list of corrections made in a branch, we leave a message with the message "merged branch-1.1.2 899-921", developers then need to determine which branch and change to view more detailed information, a tedious task.

Is there any way to avoid this? What are your strategies for preserving commit information and history between mergers.

+3
source share
3 answers

As we usually deal with this, this is the svn log branch. If you go to the branch, enter

svn log --stop-on-copy

you will get a list of each commit message for this branch, back to when the branch was formed. The stop-on-copy flag tells svn not to continue until a branch has formed.

We also use post-commit hook to email all commits to a specific stakeholder group. If you include a public mail folder there, then the history may exist forever or until the mail archive is deleted.

Read more about post-commit hooks in svn book .

+1
source

Do you know the -g option on the command line?

svn log -g ^/trunk

, . TortoiseSVN... .

+1

If you use the SVN client as Tortoise SVN, you can simply check the "Enable merged version" box

0
source

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

More articles:


All Articles