Jump to content

Mercurial

From Wikipedia, the free encyclopedia
(Redirected from Matt Mackall)

Mercurial
Developer(s)Olivia Mackall[a] (retired),[1] Pierre-Yves David
Initial release19 April 2005; 19 years ago (2005-04-19)[2]
Stable release
6.4rc0[3] Edit this on Wikidata / 2 March 2023; 8 July 2024; 1 August 2024; 28 October 2024
Repository
Written inPython, C, and Rust[4]
Operating systemUnix-like, Windows, macOS
TypeVersion control
LicenseGPL-2.0-or-later
Websitewww.mercurial-scm.org Edit this on Wikidata

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.

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[a] 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

[edit]

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

[edit]

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

[edit]

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.

Adoption

[edit]

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

[edit]

Source code hosting

[edit]

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

Open source projects using Mercurial

[edit]

Some projects using the Mercurial distributed RCS:[25]

See also

[edit]

Notes

[edit]
  1. ^ a b Olivia Mackall is formerly Matt Mackall.[6]

References

[edit]
  1. ^ "mpm - Mercurial". Mercurial. Retrieved 24 February 2023.
  2. ^ a b Mackall, Matt (20 April 2005). "Mercurial v0.1 – a minimal scalable distributed SCM". Linux kernel (Mailing list).
  3. ^ "changeset 50269:05de4896508e stable 6.4rc0".
  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 (7 January 2014). "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. ^ a b 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
[edit]