-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add extra message about starting point when performing update #445
Comments
cgwalters
added a commit
to cgwalters/bootupd
that referenced
this issue
May 5, 2023
This was easy. Closes: coreos#445
cgwalters
added a commit
to cgwalters/bootupd
that referenced
this issue
May 5, 2023
This was easy. Closes: coreos#445
travier
pushed a commit
to travier/bootupd
that referenced
this issue
Apr 16, 2024
Keep current format to avoid having to update Fedora CoreOS tests as well. Based on: coreos#472 Co-authored-by: Colin Walters <walters@verbum.org> Closes: coreos#445
travier
pushed a commit
to travier/bootupd
that referenced
this issue
Apr 17, 2024
Keep current format to avoid having to update Fedora CoreOS tests as well. Based on: coreos#472 Co-authored-by: Colin Walters <walters@verbum.org> Closes: coreos#445
travier
pushed a commit
to travier/bootupd
that referenced
this issue
Apr 19, 2024
Keep current format to avoid having to update Fedora CoreOS tests as well. Based on: coreos#472 Co-authored-by: Colin Walters <walters@verbum.org> Closes: coreos#445
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice if we could get another piece of information when running an update. Right now:
It would be nice when looking at issues later to also know what version the update started at.. i.e. something like:
The text was updated successfully, but these errors were encountered: