You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Someone from our team will open a PR later today. Thanks.
Neil Shah
CIO Data Center Services – IBM Z Specialist
Certified IT Specialist
Member of the IBM Academy of Technology
Finance and Operations
Office: 845-433-1778
Email: ***@***.******@***.***>
From: Daniel J Walsh ***@***.***>
Sent: Wednesday, September 18, 2024 11:52 AM
To: containers/podman ***@***.***>
Cc: Neil Shah ***@***.***>; Author ***@***.***>
Subject: [EXTERNAL] Re: [containers/podman] Typo in "Error: getting store info: unable to collect graph root usasge " (Issue #24001)
Interested in opening a PR? I wonder why codespell is not catching this one. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. Message ID: <containers/podman/issues/24001/2358841962@ github. com>
Interested in opening a PR?
I wonder why codespell is not catching this one.
—
Reply to this email directly, view it on GitHub<#24001 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKJ5ISUHVNOOUUDP3WNAXCDZXGOTPAVCNFSM6AAAAABON6RSNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJYHA2DCOJWGI>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
stilwelb
added a commit
to stilwelb/podman
that referenced
this issue
Sep 18, 2024
Issue Description
There is a minor typo for the word usage (usasge):
"Error: getting store info: unable to collect graph root usasge ..."
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
N/A
Describe the results you expected
Correct spelling for the word usage.
podman info output
N/A
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
N/A
Additional information
Error is in libpod/info.go line 232.
The text was updated successfully, but these errors were encountered: