From: Karel Zak <kzak@redhat.com>
To: Andreas Henriksson <andreas@fatal.se>
Cc: Ron <ron@debian.org>, 785116@bugs.debian.org, util-linux@vger.kernel.org
Subject: Re: Bug#785116: util-linux: blkid -s returns too much information
Date: Wed, 13 May 2015 12:37:06 +0200 [thread overview]
Message-ID: <20150513103706.GE4834@ws.net.home> (raw)
In-Reply-To: <20150513063604.GA466@fatal.se>
On Wed, May 13, 2015 at 08:36:04AM +0200, Andreas Henriksson wrote:
> Possibly changing the output format now could be risky.
Yes. Ron is right, the current behaviour is strange, but I'm not sure
if we want to fix it after 3 years.
And I'm also not sure it the current behavior is so big problem. If you
want just one value than it makes more sense to use
# blkid -s UUID -o value /dev/sdb1
f0710187-82bf-4646-b2e3-11b017e31218
and if you ask for more tags by "-o export" than you cannot rely on
order of the lines, so DEVNAME= in the output cannot be a problem.
> Lets ask upstream if DEVNAME is considered a tag which should
> be included in the tag filtering.... CCed.
I have a patch to fix it, but now when I think about it it's probably
better to keep the current behavior than fix one regression by
another regression ;-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-05-13 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150512132634.1127.8640.reportbug@hex.shelbyville.oz>
2015-05-13 6:36 ` Bug#785116: util-linux: blkid -s returns too much information Andreas Henriksson
2015-05-13 10:37 ` Karel Zak [this message]
2015-05-13 21:20 ` Ron
2015-05-14 6:30 ` Karel Zak
2015-05-15 9:35 ` Andreas Henriksson
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=20150513103706.GE4834@ws.net.home \
--to=kzak@redhat.com \
--cc=785116@bugs.debian.org \
--cc=andreas@fatal.se \
--cc=ron@debian.org \
--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 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.