For some reason, in 2018 i bookmarked it as a Mercurial thing. -- A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks. - GitHub - airblade/vim-gitgutter: A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
Mercurial is a free, distributed source control management tool. It efficiently handles projects of any size and offers an easy and intuitive interface.
raptus.mercurialstorage depends on Products.ExternalStorage 0.7 which has some flaws and needs to be patched in order to work correctly. The patch may be applied by using the following part in your buildout:
Backout is basically four steps rolled into one:
hg update -C -r <rev-to-backout>
hg revert --all -r <parent of rev-to-backout>
hg commit
hg update -C -r <startrev>
There's a fifth step that is done automatically if you specify --merge :
hg merge (merges <startrev> with the newly committed rev from 3.)
Mercurial keeps system wide configuration options in the file /etc/mercurial/hgrc and user configuration options in ~/.hgrc (in your home directory). We will write some user configuration options to ~/.hgrc to tweak how Mercurial works.
software version control visualization, shows history as an animated tree with the root directory of the project at its centre. Directories appear as branches with files as leaves. Developers can be seen working on the tree at the times they contributed to the project.
Andrew Morton originally developed a set of scripts for maintaining kernel patches outside of any SCM tool - quilt whose basic idea is to maintain patches instead of maintaining source files. Patches can be added, removed or reordered, and they can be refreshed as you fix bugs or update to a new base revision. quilt is very powerful, but it is not integrated with the underlying SCM tools. The patch queue extension Mq integrates quilt functionality into Mercurial. Changes are maintained as patches which are committed into Mercurial. Commits can be removed or reordered, and the underlying patch can be refreshed based on changes made in the working directory. The patch directory can also be placed under revision control, so you can have a separate history of changes made to your patches.
PMPU is oriented around the typical "Push / Pull" workflow of distributed SCMs; as such it is designed to make it easy to see what changes are arriving from remote repositories and what changes are due to be pushed upstream. It also has support for creating changeset bundles and for importing both bundles and patches; these are primarily useful when interacting with the development process via e-mail. Rather than re-invent the wheel, PMPU can make use of external history views and commit tools. For mercurial repositories, I recommend the 'hgk' or hgview viewers and the excellent Qct commit tool.
"Relying on CVS and Subversion [...] with access controls limited to the select few committers makes it very difficult for those on the fringes to get more involved."
gtools is an extension for the mercurial version control system. The extension provides a graphical user interface for status, log, and commit operations.