OSTREE-SHOW(1)

πŸ’– NAME πŸ’–

okay so this is ostree show, also known as OSTREE SHOW(1) β€” and the name line is ostree-show β€” Output a metadata object. periodt. 🫢

✨ SYNOPSIS ✨

the whole call is:

ostree show [OPTIONS...] {OBJECT}

🌸 DESCRIPTION 🌸

Given an OBJECT, it shows the metadata for that object. If you're looking at a particular revision, it will show the data for the most recent commit to that revision. no cap, that's the whole vibe. πŸ’…

πŸŽ€ OPTIONS πŸŽ€

okay bestie, options time β€” every single one, no skipping:

  • --print-related β€” shows the "related" commits. yes, with the quotes, iykyk.
  • --print-variant-type="TYPE" β€” memory-maps OBJECT (in this case a filename) to the GVariant type string. 🧚
  • --list-metadata-keys β€” lists the available metadata keys.
  • --print-metadata-key="KEY" β€” prints the string value of metadata key KEY.
  • --list-detached-metadata-keys β€” lists the available detached metadata keys.
  • --print-detached-metadata-key="KEY" β€” prints the string value of detached metadata key KEY.
  • --print-sizes β€” shows the commit size metadata. this is only supported for commits that contain ostree.sizes metadata, and it can be included when creating commits with ostree commit --generate-sizes.
  • --raw β€” shows raw variant data.
  • --gpg-homedir="HOMEDIR" β€” the GPG home directory to use when looking for keyrings (if built with GPGME - GNU Privacy Guard Made Easy). πŸ”₯

🌈 EXAMPLE 🌈

like this, bestie:

$ ostree show my-branch

            commit 67e382b11d213a402a5313e61cbc69dfd5ab93cb07
            Date:  2014-06-12 13:42:54 +0000

source/version vibe check: OSTree / OSTREE SHOW(1). the footer doesn't give a date, so we're not inventing one β€” the only date on the page is the example's 2014-06-12 13:42:54 +0000, and that's the date we're claiming. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from