REPO(1)
π REPO(1) β repo diffmanifests π
okay bestie, welcome to the Repo Manual for the repo diffmanifests command β¨ this is the one that compares your manifests and tells you what changed. buckle up π
πΈ NAME πΈ
repo β specifically the repo diffmanifests manual page, bestie. that's the whole vibe. π
β¨ SYNOPSIS β¨
repo diffmanifests manifest1.xml [manifest2.xml] [options]
π¦ DESCRIPTION π¦
Summary
Manifest diff utility π it diffs your manifests. that's it. that's the girlboss job.
π OPTIONS π
-h,--helpβ shows this help message and then dips, exit. no notes. β¨--rawβ displays the raw diff. unprocessed. unfiltered. the whole thing, no makeup π--no-colorβ does not display the diff in color. sad beige diff for sad beige terminal π--pretty-format=<FORMAT>β prints the log using a custom git pretty format string. you bring the FORMAT, it brings the log π«Ά
π Logging options:
-v,--verboseβ shows all the output. everything. every last crumb. π-q,--quietβ only shows errors. silent treatment mode, but make it functional π
π Multi-manifest options:
--outer-manifestβ operates starting at the outermost manifest. go big, go outer π«--no-outer-manifestβ does not operate on outer manifests. leave those alone fr--this-manifest-onlyβ only operates on this (sub)manifest. main character energy, no plus-ones π--no-this-manifest-only,--all-manifestsβ operates on this manifest and its submanifests. the whole friend group, everyone's invited π«
Run repo help diffmanifests to view the detailed manual. (yes, this is literally in the original, bestie β I don't make the rules π)
π DETAILS π
okay so here's the tea β the repo diffmanifests command shows differences between project revisions of manifest1 and manifest2. if manifest2 is not specified, the current manifest.xml will be used instead. both absolute and relative paths may be used for manifests β and relative paths start from project's .repo/manifests folder. iykyk π
the --raw option displays the diff in a way that facilitates parsing. so like, machine-readable vibes β¨ the project pattern will be:
<status> <path> <revision from> [<revision to>]
and the commit pattern will be:
<status> <onelined log>
with status values respectively:
A= Added projectR= Removed projectC= Changed projectU= Project with unreachable revision(s) (revision(s) not found)
for project, and
A= Added commitR= Removed commit
for a commit. π
Only changed projects may contain commits, and commit status always starts with a space, and are part of last printed project. no cap π
β οΈ Unreachable revisions may occur if project is not up to date or if repo has not been initialized with all the groups, in which case some projects won't be synced and their revisions won't be found. so likeβ¦ if stuff is missing, that's probably why, bestie π check your groups fr fr
and that's the whole page, periodt πβ¨π¦
this lil masterpiece came from the repo diffmanifests source and it's dated July 2022 β sending you off with all the love, mwah π
ππ
π¦ where this page comes from
- arch rolling: repo 2.67-1 Β· Apache-2.0
- debian bookworm: repo 2.31-1 Β· Apache-2.0
- debian trixie: repo 2.54-1 Β· Apache-2.0
- epel 9: repo 2.29.1-1.el9 Β· ASL 2.0
- fedora 43: repo 2.57.3-1.fc43 Β· Apache-2.0
- fedora 43: repo 2.68-1.fc43
- fedora 43: repo 2.69-1.fc43 Β· Apache-2.0
- fedora 44: repo 2.61.1-1.fc44 Β· Apache-2.0
- fedora 44: repo 2.68-1.fc44
- fedora 44: repo 2.69-1.fc44 Β· Apache-2.0
- ubuntu noble: repo 2.36.1-1 Β· Apache-2.0
- ubuntu noble: repo 2.36.1-1ubuntu0.1 Β· Apache-2.0
- ubuntu questing: repo 2.54-1
- ubuntu resolute: repo 2.58-4 Β· Apache-2.0
- ubuntu stonking: repo 2.58-4 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms