Mercurial

Last updated

Mercurial
Developer(s) Olivia Mackall [lower-alpha 1] (retired), [1] Pierre-Yves David
Initial release19 April 2005;18 years ago (2005-04-19) [2]
Stable release
6.6.1 [3]   OOjs UI icon edit-ltr-progressive.svg / 7 December 2023
Repository
Written in Python, C, and Rust [4]
Operating system Unix-like, Windows, macOS
Type Version control
License GPL-2.0-or-later
Website www.mercurial-scm.org   OOjs UI icon edit-ltr-progressive.svg

Mercurial is a distributed revision control tool for software developers. It is supported on Microsoft Windows, Linux, and other Unix-like systems, such as FreeBSD and macOS.

Contents

Mercurial's major design goals include high performance and scalability, decentralization, fully distributed collaborative development, robust handling of both plain text and binary files, and advanced branching and merging capabilities, while remaining conceptually simple. [5] It includes an integrated web-interface. Mercurial has also taken steps to ease the transition for users of other version control systems, particularly Subversion. Mercurial is primarily a command-line driven program, but graphical user interface extensions are available, e.g. TortoiseHg, and several IDEs offer support for version control with Mercurial. All of Mercurial's operations are invoked as arguments to its driver program hg (a reference to Hg – the chemical symbol of the element mercury).

Olivia Mackall [lower-alpha 1] originated Mercurial and served as its lead developer until late 2016. Mercurial is released as free software under the GPL-2.0-or-later license. [7] It is mainly implemented using the Python programming language, but includes a binary diff implementation written in C.

History

Mackall first announced Mercurial on 19 April 2005. [2] The impetus for this was the announcement earlier that month by Bitmover that they were withdrawing the free version of BitKeeper because of the development of SourcePuller.

BitKeeper had been used for the version control requirements of the Linux kernel project. Mackall decided to write a distributed version control system as a replacement for use with the Linux kernel. This project started a few days after the now well-known Git project was initiated by Linus Torvalds with similar aims. [8]

The Linux kernel project decided to use Git rather than Mercurial, but Mercurial is now used by many other projects (see below).

In an answer on the Mercurial mailing list, Olivia Mackall explained how the name "Mercurial" was chosen:

Shortly before the first release, I read an article about the ongoing Bitkeeper debacle that described Larry McVoy as mercurial (in the sense of 'fickle'). Given the multiple meanings, the convenient abbreviation, and the good fit with my pre-existing naming scheme (see my email address), it clicked instantly. Mercurial is thus named in Larry's honor. I do not know if the same is true of Git. [9] [10]

High-profile projects such as the OpenJDK have used Mercurial in the past, [11] though the OpenJDK no longer does as of Java 16.

Design

Mercurial uses SHA-1 hashes to identify revisions. For repository access via a network, Mercurial uses an HTTP-based protocol that seeks to reduce round-trip requests, new connections, and data transferred. Mercurial can also work over SSH where the protocol is very similar to the HTTP-based protocol. By default it uses a 3-way merge before calling external merge tools.

Usage

Figure 1 shows some of the most important operations in Mercurial and their relations to Mercurial's concepts.

Figure 1: Some important operations of Mercurial and their relations. Mercurial commandd and their relations.png
Figure 1: Some important operations of Mercurial and their relations.

Adoption

Although Mercurial was not selected to manage the Linux kernel sources, it has been adopted by several organizations, including Facebook, [12] the W3C, and Mozilla. Facebook is using the Rust programming language to write Mononoke, [13] [14] a Mercurial server specifically designed to support large multi-project repositories.

In 2013, Facebook adopted Mercurial and began work on scaling it to handle their large, unified code repository. [15]

Google also uses Mercurial client as a front-end on their cloud-based 'Piper' monorepo back-end. [16]

Bitbucket announced that its web-based version control services would end support for Mercurial in June 2020 (then extended to July 2020), [17] explaining that "less than 1% of new projects use it, and developer surveys indicated that 90% of developers use Git". [18]

Mercurial servers and repository management

Source code hosting

The following websites provide free source code hosting for Mercurial repositories:

Open source projects using Mercurial

Some projects using the Mercurial distributed RCS: [25]

See also

Notes

  1. 1 2 Olivia Mackall is formerly Matt Mackall. [6]

Related Research Articles

BitKeeper is a discontinued software tool for distributed revision control of computer source code. Originally developed as proprietary software by BitMover Inc., a privately held company based in Los Gatos, California, it was released as open-source software under the Apache-2.0 license on 9 May 2016. BitKeeper is no longer being developed.

<span class="mw-page-title-main">Monotone (software)</span> Revision control software

Monotone is an open source software tool for distributed revision control.

<span class="mw-page-title-main">Git</span> Software for version control of files

Git is a distributed version control system that tracks changes in any set of computer files, usually used for coordinating work among programmers who are collaboratively developing source code during software development. Its goals include speed, data integrity, and support for distributed, non-linear workflows.

In software development, distributed version control is a form of version control in which the complete codebase, including its full history, is mirrored on every developer's computer. Compared to centralized version control, this enables automatic management branching and merging, speeds up most operations, improves the ability to work offline, and does not rely on a single location for backups. Git, the world's most popular version control system, is a distributed version control system.

In software development, a codebase is a collection of source code used to build a particular software system, application, or software component. Typically, a codebase includes only human-written source code system files; thus, a codebase usually does not include source code files generated by tools or binary library files, as they can be built from the human-written source code. However, it generally does include configuration and property files, as they are the data necessary for the build.

A source-code-hosting facility is a file archive and web hosting facility for source code of software, documentation, web pages, and other works, accessible either publicly or privately. They are often used by open-source software projects and other multi-developer projects to maintain revision and version history, or version control. Many repositories provide a bug tracking system, and offer release management, mailing lists, and wiki-based project documentation. Software authors generally retain their copyright when software is posted to a code hosting facilities.

<span class="mw-page-title-main">Buildbot</span> Continuous integration testing framework

Buildbot is a software development continuous integration tool which automates the compile or test cycle required to validate changes to the project code base. It began as a light-weight alternative to the Mozilla project's Tinderbox, and is now used by Python, WebKit, LLVM, Blender, ReactOS, and many other projects.

In software development, version control is a class of systems responsible for managing changes to computer programs or other collections of information such that revisions have a logical and consistent organization. The following tables include general and technical information on notable version control and software configuration management (SCM) software. For SCM software not suitable for source code, see Comparison of open-source configuration management software.

<span class="mw-page-title-main">GNU Bazaar</span>

GNU Bazaar is a distributed and client–server revision control system sponsored by Canonical.

<span class="mw-page-title-main">GNU IceCat</span> Firefox derivative recommending only free software

GNU IceCat, formerly known as GNU IceWeasel, is a completely free version of the Mozilla Firefox web browser distributed by the GNU Project. It is compatible with Linux, Windows, Android and macOS.

License compatibility is a legal framework that allows for pieces of software with different software licenses to be distributed together. The need for such a framework arises because the different licenses can contain contradictory requirements, rendering it impossible to legally combine source code from separately-licensed software in order to create and publish a new program. Proprietary licenses are generally program-specific and incompatible; authors must negotiate to combine code. Copyleft licenses are commonly deliberately incompatible with proprietary licenses, in order to prevent copyleft software from being re-licensed under a proprietary license, turning it into proprietary software. Many copyleft licenses explicitly allow relicensing under some other copyleft licenses. Permissive licenses are compatible with everything, including proprietary licenses; there is thus no guarantee that all derived works will remain under a permissive license.

Quilt is a software utility for managing a series of changes to the source code of any computer program. Such changes are often referred to as "patches" or "patch sets". Quilt can take an arbitrary number of patches as input and condense them into a single patch. In doing so, Quilt makes it easier for many programmers to test and evaluate the different changes amongst patches before they are permanently applied to the source code.

Bitbucket is a Git-based source code repository hosting service owned by Atlassian. Bitbucket offers both commercial plans and free accounts with an unlimited number of private repositories.

<span class="mw-page-title-main">TortoiseHg</span>

TortoiseHg is a GUI front-end for Mercurial that runs on Microsoft Windows, Mac OS X, and Linux.

Plastic SCM is a cross-platform commercial distributed version control tool developed by Códice Software Inc. It is available for Microsoft Windows, Mac OS X, Linux, and other operating systems. It includes a command-line tool, native GUIs, diff and merge tool and integration with a number of IDEs. It is a full version control stack not based on Git.

In version control systems, a repository is a data structure that stores metadata for a set of files or directory structure. Depending on whether the version control system in use is distributed, like Git or Mercurial, or centralized, like Subversion, CVS, or Perforce, the whole set of information in the repository may be duplicated on every user's system or may be maintained on a single server. Some of the metadata that a repository contains includes, among other things, a historical record of changes in the repository, a set of commit objects, and a set of references to commit objects, called heads.

In version control systems, a commit is an operation which sends the latest changes of the source code to the repository, making these changes part of the head revision of the repository. Unlike commits in data management, commits in version control systems are kept in the repository indefinitely. Thus, when other users do an update or a checkout from the repository, they will receive the latest committed version, unless they specify that they wish to retrieve a previous version of the source code in the repository. Version control systems allow rolling back to previous versions easily. In this context, a commit within a version control system is protected as it is easily rolled back, even after the commit has been applied.

In version-control systems, a monorepo is a software-development strategy in which the code for a number of projects is stored in the same repository. This practice dates back to at least the early 2000s, when it was commonly called a shared codebase. Google, Meta, Microsoft, Uber, Airbnb, and Twitter all employ very large monorepos with varying strategies to scale build systems and version control software with a large volume of code and daily changes.

References

  1. ↑ "mpm - Mercurial". Mercurial. Retrieved 24 February 2023.
  2. 1 2 Mackall, Matt (20 April 2005). "Mercurial v0.1 – a minimal scalable distributed SCM". Linux kernel (Mailing list).
  3. ↑ "Mercurial tag 6.6.1".
  4. ↑ "README file in rust subdirectory, master branch". 24 January 2020. Retrieved 30 January 2020.
  5. ↑ Mackall, Matt. "Towards a Better SCM: Revlog and Mercurial" (PDF). Mercurial. Archived (PDF) from the original on 26 May 2019. Retrieved 26 May 2019.
  6. ↑ "Matt Mackall is now Olivia Mackall". Mercurial. Retrieved 28 May 2021.
  7. ↑ "Relicensing", Mercurial (wiki), Mercurial-scm.org.
  8. ↑ Mackall, Matt (29 April 2005). "Re: Mercurial 0.4b vs git patchbomb benchmark". Linux kernel (Mailing list). Archived from the original on 9 July 2012.
  9. ↑ Mackall, Matt (15 February 2012). "Why did Matt choose the name Mercurial?". Mercurial (Mailing list). Retrieved 7 June 2016.
  10. ↑ Torvalds has said: "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git."
  11. ↑ James Gosling (October 2006). "Open Sourcing Sun's Java Platform Implementations, Part 1" (Interview). Interviewed by Robert Eckstein. Sun. Archived from the original on 1 March 2009.{{cite interview}}: CS1 maint: unfit URL (link)
  12. ↑ "Scaling Mercurial at Facebook". 7 January 2014.
  13. ↑ "A Mercurial source control server, specifically designed to support large monorepos.: facebookexperimental/mononoke". 31 January 2019 – via GitHub.
  14. ↑ Szorc, Gregory (17 October 2016). "Mercurial 4.0 Sprint Notes". mozilla.dev.version-control. Google Groups . Retrieved 2021-11-22.
  15. ↑ Goode, Durham; Agarwal, Siddharth. "Scaling Mercurial at Facebook". Facebook Code. Retrieved 13 October 2015– via Facebook.
  16. ↑ "Why Google Stores Billions of Lines of Code in a Single Repository".
  17. ↑ "Sunsetting Mercurial support in Bitbucket". 21 April 2020. Archived from the original on 1 July 2020.
  18. 1 2 Chan, Denise (20 August 2019). "Sunsetting Mercurial support in Bitbucket". Bitbucket. Retrieved 29 August 2019.
  19. ↑ "Git, Mercurial & Subversion hosting". Features. Codebase HQ. 4 March 2013. Archived from the original on 30 March 2014. Retrieved 4 March 2013.
  20. ↑ "Let's start OSS development with Mercurial (Hg) – OSDN". osdn.net.
  21. ↑ "Hosting", Mercurial (wiki), Mercurial-scm.org.
  22. ↑ "Try Helix TeamHub Free | Perforce". info.perforce.com.
  23. ↑ "Welcome [Puszcza]". ps.gnu.org.ua.
  24. ↑ "TuxFamily: Free hosting for free people". tuxfamily.org.
  25. ↑ "Some projects that use Mercurial", Mercurial (wiki), Mercurial-scm.org.
  26. ↑ Reed, J Paul (12 April 2007). "Version Control System Shootout Redux Redux".
  27. ↑ mozilla-mobile/fenix, Mozilla Mobile, 19 March 2021, retrieved 19 March 2021
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.