HG(INCOMING)
π HG(INCOMING) β or like, the whole hg incoming manual page bestie π
okay so this is the HG(INCOMING) manual page, and it's literally all about peeking at what's new before you commit to pulling it. iconic behavior tbh β¨
πΈ NAME πΈ
hg incoming β show new changesets found in source
π SYNOPSIS π
hg incoming [-p] [-n] [-M] [-f] [-r REV]... [--bundle FILENAME] [SOURCE]
π¦ DESCRIPTION π¦
So like, this shows you the new changesets hanging out in the path/URL you point at, or in the default pull location if you don't point at anything. These are exactly the changesets that hg pull would have grabbed at the moment you ran this command. It's giving β¨preview modeβ¨.
See pull for valid source format details. (yes bestie, go read that one too, it's the whole vibe for how sources work π
)
π bookmark comparison, when you pass -B/--bookmarks
With -B/--bookmarks, you get the result of the bookmark comparison between your local repo and the remote one. And with -v/--verbose, the status also gets displayed for each bookmark, like this:
BM1 01234567890a added
BM2 1234567890ab advanced
BM3 234567890abc diverged
BM4 34567890abcd changed
The action taken locally when pulling depends on the status of each bookmark:
- added β pull will create it
- advanced β pull will update it
- diverged β pull will create a divergent bookmark
- changed β result depends on remote changesets
- From the point of view of pulling behavior, bookmark existing only in the remote repository are treated as added, even if it is in fact locally deleted.
- For remote repository, using
--bundleavoids downloading the changesets twice if the incoming is followed by a pull.
π examples, because we love a demo
Examples:
- show incoming changes with patches and full description:
hg incoming -vp
- show incoming changes excluding merges, store a bundle:
hg in -vpM --bundle incoming.hg
hg pull incoming.hg
- briefly list changes inside a bundle:
hg in changes.hg -T "{desc|firstline}\n"
Returns 0 if there are incoming changes, 1 otherwise. π
β¨ OPTIONS β¨
-f,--forceβ run even if remote repository is unrelated-n,--newest-firstβ show newest record first--bundle <FILE>β file to store the bundles into-r,--rev <REV[+]>β a remote changeset intended to be added-B,--bookmarksβ compare bookmarks-b,--branch <BRANCH[+]>β a specific branch you would like to pull--remote-hiddenβ include changesets hidden on the remote (EXPERIMENTAL)-p,--patchβ show patch-g,--gitβ use git extended diff format-l,--limit <NUM>β limit number of changes displayed-M,--no-mergesβ do not show merges--statβ output diffstat-style summary of changes-G,--graphβ show the revision DAG--style <STYLE>β display using template map file (DEPRECATED)-T,--template <TEMPLATE>β display with template-e,--ssh <CMD>β specify ssh command to use--remotecmd <CMD>β specify hg command to run on the remote side--insecureβ do not verify server certificate (ignoringweb.cacertsconfig)-S,--subreposβ recurse into subrepositories
[+] marked option can be specified multiple times π«Ά
π ALIASES π
in
k that's the whole page bestie, no notes π
and yeah, the footer just says HG(INCOMING) again β same as the header up top β so consider this your lil sign-off from the HG(INCOMING) page itself. mwah ππ
π¦ where this page comes from
- arch rolling: mercurial 7.2.4-1 Β· GPL
- fedora 44: mercurial 7.2-1.fc44 Β· GPL-2.0-or-later
- fedora 44: mercurial 7.2.4-1.fc44 Β· GPL-2.0-or-later
- nixpkgs unstable: mercurial 7.2.2
- nixpkgs unstable: mercurial-full 7.2.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms