Difference between revisions of "Applications/Mercurial"
From HPC
m (Pysdlb moved page Application/Mercurial to Applications/Mercurial without leaving a redirect) |
m |
||
Line 51: | Line 51: | ||
* [https://www.mercurial-scm.org/ https://www.mercurial-scm.org/] | * [https://www.mercurial-scm.org/ https://www.mercurial-scm.org/] | ||
− | + | ||
− | + | ==Navigation== | |
− | + | ||
* [[Main_Page|Home]] | * [[Main_Page|Home]] | ||
− | * [[Applications|Application support]] | + | * [[Applications|Application support]] * |
* [[General|General]] | * [[General|General]] | ||
− | |||
* [[Programming|Programming support]] | * [[Programming|Programming support]] | ||
− | |||
− |
Revision as of 13:13, 24 May 2019
Contents
Application Details
- Description: Mercurial efficiently handles projects of any size and kind. Every clone contains the whole project history, so most actions are local, fast and convenient. Mercurial supports a multitude of workflows and you can easily enhance its functionality with extensions.
- Version: 3.9.1
- Modules: mercurial/3.9.1
- Licence: licensed under GPLv2
Usage Examples
Distributed architecture
Traditional version control systems such as Subversion are typical client-server architectures with a central server to store the revisions of a project. In contrast, Mercurial is truly distributed, giving each developer a local copy of the entire development history. This way it works independent of network access or a central server. Committing, branching and merging are fast and cheap.
To access in an interactive or non-interactive (using SLURM), you will need to load the module.
[username@gpu01 ~]$ module mercurial/3.9.1
Clone a project and push changes
$ hg clone https://www.mercurial-scm.org/repo/hello $ cd hello $ (edit files) $ hg add (new files) $ hg commit -m 'My changes' $ hg push
Create a project and commit
$ hg init (project-directory) $ cd (project-directory) $ (add some files) $ hg add $ hg commit -m 'Initial commit'
Further Information