From: Stefan Hajnoczi <stefanha@redhat.com>
To: linux-block@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Jeff Moyer <jmoyer@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 0/2] spec: liburing-2.0 updates
Date: Tue, 9 Mar 2021 14:19:11 +0000 [thread overview]
Message-ID: <20210309141913.262131-1-stefanha@redhat.com> (raw)
Update the liburing.spec file so the liburing.pc pkg-config file and rpms
report version 2.0 instead of 0.7.
Stefan Hajnoczi (2):
spec: bump version to 2.0
spec: add explicit build dependency on make
liburing.spec | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.29.2
next reply other threads:[~2021-03-09 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 14:19 Stefan Hajnoczi [this message]
2021-03-09 14:19 ` [PATCH 1/2] spec: bump version to 2.0 Stefan Hajnoczi
2021-03-09 14:19 ` [PATCH 2/2] spec: add explicit build dependency on make Stefan Hajnoczi
2021-03-09 15:00 ` [PATCH 0/2] spec: liburing-2.0 updates 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 \
--in-reply-to=20210309141913.262131-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).