From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-block/fio/
Date: Sat, 7 Nov 2020 01:19:38 +0000 (UTC) [thread overview]
Message-ID: <1604711945.966b0882e77e32cc6d451ec3200781c28c2adde8.sam@gentoo> (raw)
commit: 966b0882e77e32cc6d451ec3200781c28c2adde8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 7 01:12:54 2020 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 7 01:19:05 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=966b0882
sys-block/fio: revbump for liburing subslot op
Bug: https://bugs.gentoo.org/752132
Acked-by: David Seifert <soap <AT> gentoo.org>
Package-Manager: Portage-3.0.8, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-block/fio/{fio-3.20-r1.ebuild => fio-3.20-r2.ebuild} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/sys-block/fio/fio-3.20-r1.ebuild b/sys-block/fio/fio-3.20-r2.ebuild
similarity index 100%
rename from sys-block/fio/fio-3.20-r1.ebuild
rename to sys-block/fio/fio-3.20-r2.ebuild
next reply other threads:[~2020-11-07 1:19 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 1:19 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 21:20 [gentoo-commits] repo/gentoo:master commit in: sys-block/fio/ Andreas K. Hüttel
2024-10-12 10:08 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 7:52 Michał Górny
2024-08-12 15:04 Guilherme Amadio
2024-05-29 6:26 Jakov Smolić
2024-05-28 20:49 Sam James
2024-05-23 1:36 Sam James
2024-05-22 1:06 Sam James
2024-03-07 14:08 Robin H. Johnson
2023-05-16 1:52 Sam James
2023-05-03 6:33 Arthur Zamarin
2023-05-03 4:45 Sam James
2023-05-02 20:50 Sam James
2023-05-02 20:15 Sam James
2023-05-01 8:47 Sam James
2023-04-13 5:53 Robin H. Johnson
2022-10-18 2:55 Sam James
2022-08-19 4:04 Sam James
2022-05-19 7:28 WANG Xuerui
2022-04-15 19:35 Robin H. Johnson
2022-04-15 19:35 Robin H. Johnson
2022-04-15 6:27 Sam James
2022-04-15 4:57 Robin H. Johnson
2022-03-28 17:46 Robin H. Johnson
2022-02-15 9:24 Jakov Smolić
2022-01-14 17:36 Jakov Smolić
2022-01-04 3:22 Sam James
2022-01-03 12:37 Sam James
2022-01-03 12:36 Sam James
2022-01-03 12:11 Jakov Smolić
2022-01-03 12:11 Jakov Smolić
2021-08-06 15:13 Matthew Thode
2021-07-05 20:02 Matthew Thode
2021-06-08 2:58 Matthew Thode
2021-06-07 4:18 Matthew Thode
2021-05-02 16:12 Mikle Kolyada
2021-02-13 10:27 David Seifert
2021-02-02 4:20 Sam James
2021-02-01 8:25 Sam James
2021-01-31 18:48 Sam James
2021-01-30 16:22 Sam James
2021-01-30 14:29 Sam James
2021-01-25 14:18 Sam James
2020-11-07 1:19 Sam James
2020-11-06 10:26 Lars Wendler
2020-07-02 22:31 Lars Wendler
2020-07-02 20:24 Robin H. Johnson
2020-05-07 17:58 Michał Górny
2020-05-03 12:58 Agostino Sarubbo
2020-05-03 12:31 Agostino Sarubbo
2020-05-03 12:30 Agostino Sarubbo
2020-05-03 12:30 Agostino Sarubbo
2020-05-03 12:28 Agostino Sarubbo
2020-04-20 22:49 Matthew Thode
2020-03-13 6:08 Robin H. Johnson
2020-01-24 18:39 Mike Frysinger
2018-11-18 11:20 Justin Lecher
2018-06-25 13:20 Thomas Deutschmann
2017-12-02 20:51 Justin Lecher
2017-11-30 18:47 Robin H. Johnson
2017-08-19 16:20 Sergei Trofimovich
2017-04-20 16:41 David Seifert
2017-02-05 16:52 Markus Meier
2017-01-05 22:50 Justin Lecher
2017-01-03 10:38 Agostino Sarubbo
2016-12-30 11:12 Agostino Sarubbo
2016-12-28 8:13 Aaron Bauman
2016-11-08 18:33 Robin H. Johnson
2016-06-29 22:33 Alexey Shvetsov
2016-04-20 17:02 Mike Frysinger
2016-01-22 21:03 Robin H. Johnson
2015-11-12 10:11 Agostino Sarubbo
2015-10-17 11:17 Markus Meier
2015-10-04 10:17 Jeroen Roovers
2015-10-01 3:19 Mike Frysinger
2015-09-30 13:43 Agostino Sarubbo
2015-09-29 10:18 Agostino Sarubbo
2015-09-28 16:18 Mike Frysinger
2015-09-28 16:18 Mike Frysinger
2015-09-28 16:13 Mike Frysinger
2015-09-28 16:04 Mike Frysinger
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 \
--in-reply-to=1604711945.966b0882e77e32cc6d451ec3200781c28c2adde8.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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