How to Install and Uninstall git-merge-changelog Package on openSUSE Leap

Last updated: November 26,2024

1. Install "git-merge-changelog" package

This tutorial shows how to install git-merge-changelog on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                git-merge-changelog
            
                    
    
    Copied

2. Uninstall "git-merge-changelog" package

Learn how to uninstall git-merge-changelog on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                git-merge-changelog
            
                    
    
    Copied

3. Information about the git-merge-changelog package on openSUSE Leap

Information for package git-merge-changelog:
--------------------------------------------
Repository : Main Repository
Name : git-merge-changelog
Version : 20120413-bp155.2.10
Arch : x86_64
Vendor : openSUSE
Installed Size : 70.9 KiB
Installed : No
Status : not installed
Source package : git-merge-changelog-20120413-bp155.2.10.src
Upstream URL : http://www.gnu.org/software/gnulib
Summary : Git merge driver for ChangeLog files
Description :
Git merge driver for ChangeLog files.
1. It produces no conflict when ChangeLog entries have been inserted
at the top both in the public and in the private modification. It
puts the privately added entries above the publicly added entries.
2. It respects the structure of ChangeLog files: entries are not split
into lines but kept together.
3. It also handles the case of small modifications of past ChangeLog
entries, or of removed ChangeLog entries: they are merged as one
would expect it.
4. Conflicts are presented at the top of the file, rather than where
they occurred, so that the user will see them immediately. (Unlike
for source code written in some programming language, conflict markers
that are located several hundreds lines from the top will not cause
any syntax error and therefore would be likely to remain unnoticed.)