linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	linux-block@vger.kernel.org,
	Aarushi Mehta <mehta.aaru20@gmail.com>,
	Julia Suvorova <jusual@mail.ru>
Subject: Re: liburing 0.2 release?
Date: Fri, 25 Oct 2019 08:31:41 -0400	[thread overview]
Message-ID: <x49h83xc8gi.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <568a4400-94d9-8b31-43bd-bd28e405f36f@kernel.dk> (Jens Axboe's message of "Thu, 24 Oct 2019 20:24:30 -0600")

Jens Axboe <axboe@kernel.dk> writes:

> On 10/21/19 9:49 AM, Jens Axboe wrote:
>> On 10/21/19 9:47 AM, Jeff Moyer wrote:
>>> Jens Axboe <axboe@kernel.dk> writes:
>>>
>>>> On 10/9/19 2:34 AM, Stefan Hajnoczi wrote:
>>>>> Hi Jens,
>>>>> I would like to add a liburing package to Fedora.  The liburing 0.1
>>>>> release was in January and there have been many changes since then.  Is
>>>>> now a good time for a 0.2 release?
>>>>
>>>> I've been thinking the same. I'll need to go over the 0.1..0.2 additions
>>>> and ensure I'm happy with all of it (before it's set in stone), then we
>>>> can tag 0.2.
>>>>
>>>> Let's aim for a 0.2 next week at the latest.
>>>
>>> ping?
>> 
>> Still on the radar, just got dragged out a bit with the changes last week.
>> Let's aim for this week :-)
>
> OK, I think we're good to go. I tagged and pushed out 0.2 just now.

Thanks!
Jeff


      reply	other threads:[~2019-10-25 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  8:34 liburing 0.2 release? Stefan Hajnoczi
2019-10-09 11:40 ` Jens Axboe
2019-10-09 17:46   ` Stefan Hajnoczi
2019-10-21 15:47   ` Jeff Moyer
2019-10-21 15:49     ` Jens Axboe
2019-10-25  2:24       ` Jens Axboe
2019-10-25 12:31         ` Jeff Moyer [this message]

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=x49h83xc8gi.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=jusual@mail.ru \
    --cc=linux-block@vger.kernel.org \
    --cc=mehta.aaru20@gmail.com \
    --cc=stefanha@redhat.com \
    /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).