From: hch@lst.de (Christoph Hellwig)
Subject: nvme-cli code quality
Date: Wed, 13 Jun 2018 09:53:11 +0200 [thread overview]
Message-ID: <20180613075311.GA22867@lst.de> (raw)
Hi Keith,
can we please enforce linux-nvme list based reviews for nvme-cli?
It seems like a lot of code gets merged really quickly while still in
horrible shape (e.g. the recent seagate plugin, not that other plugins
are that great either).
I think we should try to enforce our normal quality requirements instead
of letting it turn into a huge mess. Especially as reviews on a closed
platform like github just don't seem to work at all.
reply other threads:[~2018-06-13 7:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180613075311.GA22867@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