Skip to content

Conversation

@cgmcintyr
Copy link
Collaborator

closes #72

@jberkus
Copy link
Contributor

jberkus commented Aug 30, 2017

Hold on to this, we kind of messed up the repo directory structure. Will merge once we fix it.

<< History beyond this commit not fetched >>
....

This ref has one commit in its history.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you interested in adding some information on how to download history that is not currently fetched?

Something like this: https://github.com/dustymabe/dustymabe.com/blob/33a300f3b31c7126b69a6d56487d251b776522ef/content/post/2017-09-01/post.md#browsing-histroy

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I'm happy to do that when I next get some spare time :)

To check which ref is currently checked out, run `ostree admin status`:

....
$ ostree admin status
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we also show the output of rpm-ostree status here and show the user that they essentially show the same output?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as their isn't an rpm-ostree section, it makes sense to add that in here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using OSTree / Examining Your System

3 participants