From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: nvmetcli release?
Date: Mon, 30 Oct 2023 14:26:20 +0100 [thread overview]
Message-ID: <20231030132620.GA21741@lst.de> (raw)
In-Reply-To: <uvqke5sw2nqf63vuwypemyrllpr7h4le3jjzcxsbuavja6xhbn@tpqilzrlwh7a>
On Mon, Oct 30, 2023 at 01:29:52PM +0100, Daniel Wagner wrote:
> Hi Christoph,
>
> Would it possible to a new release of nvmetcli? Just asking because I
> was asked to update our downstream package to latest version. It would
> make it slightly simpler if there is a new release.
I'll try to cut one this week, a release has been long overdue.
prev parent reply other threads:[~2023-10-30 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 12:29 nvmetcli release? Daniel Wagner
2023-10-30 13:26 ` Christoph Hellwig [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=20231030132620.GA21741@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=linux-nvme@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.