From: hch@lst.de (Christoph Hellwig)
Subject: nvme-cli: tag new version?
Date: Thu, 10 Jan 2019 08:56:26 +0100 [thread overview]
Message-ID: <20190110075626.GA2331@lst.de> (raw)
In-Reply-To: <cda3e67e-2e0f-24f4-4dd6-e49167d0b3e3@suse.de>
On Thu, Jan 10, 2019@08:49:48AM +0100, Hannes Reinecke wrote:
> Hi Keith,
>
> wouldn't it be a good time to tag a new version?
> We've gotten full ANA support and the TCP transport in, so I guess it'll
> warrant a new version...
Btw, still waiting for an updated nvmetcli ANA patch, a new version
with that is long overdue as well.
next prev parent reply other threads:[~2019-01-10 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 7:49 nvme-cli: tag new version? Hannes Reinecke
2019-01-10 7:56 ` Christoph Hellwig [this message]
2019-01-10 14:52 ` Keith Busch
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=20190110075626.GA2331@lst.de \
--to=hch@lst.de \
/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