From: hch@infradead.org (Christoph Hellwig)
Subject: [ANNOUNCE] nvmetcli 0.2 release
Date: Wed, 12 Oct 2016 00:47:21 -0700 [thread overview]
Message-ID: <20161012074721.GA7632@infradead.org> (raw)
In-Reply-To: <20161012074434.i4t6dumb6ocrluiy@linux-x5ow.site>
On Wed, Oct 12, 2016@09:44:35AM +0200, Johannes Thumshirn wrote:
> Small nit, can you bump the version number in setup.py when doing v0.3.
I'm not used to doing releases for python code yet :) Will do it, or
rather find a way to automate it.
prev parent reply other threads:[~2016-10-12 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 14:59 [ANNOUNCE] nvmetcli 0.2 release Christoph Hellwig
2016-10-12 7:44 ` Johannes Thumshirn
2016-10-12 7:47 ` 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=20161012074721.GA7632@infradead.org \
--to=hch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox