From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Kanna Scarlet <[email protected]>,
Fernanda Ma'rouf <[email protected]>,
io-uring Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: [GIT PULL] GitHub bot update
Date: Wed, 10 Aug 2022 07:55:22 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Jens,
Just a single commit to upgrade the OS on the GitHub bot CI.
"ubuntu-latest" doesn't give the latest version of Ubuntu. Explicitly
specify "ubuntu-22.04" to get the latest version. This is just like
commit:
f642f8fd71bf (".github: Upgrade GitHub bot to Ubuntu 22.04 and gcc-11")
... but for the shellcheck.
Please pull!
---
The following changes since commit 2757d61fa222739f77b014810894b9ccea79d7f3:
io_uring-udp: make more obvious what kernel version is required (2022-08-05 08:43:23 -0600)
are available in the Git repository at:
https://github.com/ammarfaizi2/liburing.git tags/github-bot-2022-08-10
for you to fetch changes up to 487604001a46441888469df44c081e08afd5e3c5:
.github: Update OS to Ubuntu 22.04 for shellcheck CI (2022-08-10 07:53:14 +0700)
----------------------------------------------------------------
Just a single commit to upgrade the OS on the GitHub bot CI.
"ubuntu-latest" doesn't give the latest version of Ubuntu. Explicitly
specify "ubuntu-22.04" to get the latest version. This is just like
commit:
f642f8fd71bf (".github: Upgrade GitHub bot to Ubuntu 22.04 and gcc-11")
... but for the shellcheck.
----------------------------------------------------------------
Ammar Faizi (1):
.github: Update OS to Ubuntu 22.04 for shellcheck CI
.github/workflows/shellcheck.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Ammar Faizi
next reply other threads:[~2022-08-10 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 0:55 Ammar Faizi [this message]
2022-08-10 13:01 ` [GIT PULL] GitHub bot update Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox