From: Dan Mick <dmick@redhat.com>
To: util-linux@vger.kernel.org
Subject: lsblk '--allcols'
Date: Fri, 20 Apr 2018 14:42:33 -0700 [thread overview]
Message-ID: <cf949a43-9027-de52-87e2-33c95605d58b@redhat.com> (raw)
Beyond simple "show me a quick overview", I often want to see everything
the system knows about a blockdev, and it's a drag to have to construct
the option list from the output of help. I've made a simple
"-A/--allcols" patch. Is that something that would meet the
expectations of the team, and if so, is email to this list the best way
to submit it?
next reply other threads:[~2018-04-20 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 21:42 Dan Mick [this message]
2018-04-21 8:14 ` lsblk '--allcols' Sami Kerola
2018-04-23 9:46 ` Karel Zak
2018-04-24 21:38 ` Sami Kerola
2018-05-10 10:25 ` Karel Zak
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=cf949a43-9027-de52-87e2-33c95605d58b@redhat.com \
--to=dmick@redhat.com \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).