HG(INCOMING)

πŸ“¦
version 7.2.4 Β· 2 versions
, in arch rolling, fedora 44, nixpkgs unstable

πŸ’– 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 --bundle avoids 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 (ignoring web.cacerts config)
  • -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