Mercurial

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

Mercurial
Developer(s)Matt Mackall
Initial release19 April 2005 (2005-04-19)[1]
Stable release
5.5 / 3 August 2020 (2020-08-03)[2]
Repository
Written inPython, C, and Rust[3]
Operating systemUnix-like, Windows, macOS
TypeVersion control
LicenseGNU GPL v2+
Websitewww.mercurial-scm.org 

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.[4] 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).

Matt Mackall originated Mercurial and served as its lead developer until late 2016. Mercurial is released as free software under the terms of the GNU GPL v2 (or any later version[5]). 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.[1] 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.[6]

The Linux kernel project decided to use Git rather than Mercurial, but Mercurial is now used by many other projects (see below). "Git vs. Mercurial" has become one of the holy wars of hacker culture.[7]

In an answer on the Mercurial mailing list, Matt 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.[8][9]

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.

Adoption

Although Mercurial was not selected to manage the Linux kernel sources, it has been adopted by several organizations, including Facebook,[10] the W3C, and Mozilla. Facebook is using the Rust programming language to write Mononoke,[11][12] 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.[13]

Bitbucket announced that its web-based version control services would end support for Mercurial in June 2020 (then changed to July 2020, and then extended to 2020-07-08[14]), explaining that "less than 1% of new projects use it, and developer surveys indicated that 90% of developers use Git."[15], while hundreds of users openly questioned the reasoning for massively deleting historical data, asked why there was not significant warning nor a formal migration plan, and paniced about the rushed timing in their official company support thread.[16]

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]

gollark: Phones really have gotten somewhat overly large, as they say.
gollark: Fascinating.
gollark: An *actual* Google phone or just an Android one you're referring to wrongly?
gollark: I agree.
gollark: Saddening.

See also

References
  1. Mackall, Matt (20 April 2005). "Mercurial v0.1 – a minimal scalable distributed SCM". Linux kernel (Mailing list).
  2. Goyal, Pulkit (3 August 2020). "Mercurial 5.5 tagged". mercurial-packaging (Mailing list). Retrieved 3 August 2020.
  3. "README file in rust subdirectory, master branch". 24 January 2020. Retrieved 30 January 2020.
  4. Mackall, Matt. "Towards a Better SCM: Revlog and Mercurial" (PDF). Mercurial. Archived (PDF) from the original on 26 May 2019. Retrieved 26 May 2019.
  5. "Relicensing", Mercurial (wiki), Mercurial-scm.org.
  6. 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.
  7. "Managing source code with Mercurial". Mercurial and Git fans are also happy to discuss the learning curve, merits, and usability of each VCS system's command set. Space prevents that discussion here, but a web search on that topic will provide lots of interesting reading material.
  8. Mackall, Matt (15 February 2012). "Why did Matt choose the name Mercurial?". Mercurial (Mailing list). Retrieved 7 June 2016.
  9. Torvalds has said: "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git."
  10. "Scaling Mercurial at Facebook". 7 January 2014.
  11. "A Mercurial source control server, specifically designed to support large monorepos.: facebookexperimental/mononoke". 31 January 2019 – via GitHub.
  12. "Google Groups". groups.google.com.
  13. Goode, Durham; Agarwal, Siddharth. "Scaling Mercurial at Facebook". Facebook Code. Facebook. Retrieved 13 October 2015.
  14. . 1 July 2020 https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket. Archived from the original on 1 July 2020. Missing or empty |title= (help)
  15. Chan, Denise (20 August 2019). "Sunsetting Mercurial support in Bitbucket". Bitbucket. Retrieved 29 August 2019.
  16. "What to do with your Mercurial repos when Bitbucket sunsets support". |archive-url= is malformed: timestamp (help) Alt URL
  17. "Git, Mercurial & Subversion hosting". Features. Codebase HQ. 4 March 2013. Archived from the original on 30 March 2014. Retrieved 4 March 2013.
  18. "Welcome [Puszcza]". ps.gnu.org.ua.
  19. "Let's start OSS development with Mercurial (Hg) - OSDN". osdn.net.
  20. "Try Helix TeamHub Free | Perforce". info.perforce.com.
  21. "TuxFamily: Free hosting for free people". www.tuxfamily.org.
  22. "GitHub - ianchanning/awesome-github-alternatives: Love 'em or leave 'em". github.com.
  23. "hg.sr.ht". hg.sr.ht.
  24. "Hosting", Mercurial (wiki), Mercurial-scm.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. 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.CS1 maint: unfit url (link)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.