public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Stanislav Brabec <sbrabec@suse.cz>
Cc: util-linux@vger.kernel.org
Subject: Re: libblkid: check for ext* is deeply broken
Date: Wed, 9 Apr 2014 09:43:42 +0200	[thread overview]
Message-ID: <20140409074342.GO22126@x2.net.home> (raw)
In-Reply-To: <1396993958.14732.144.camel@oct.suse.cz>

On Tue, Apr 08, 2014 at 11:52:38PM +0200, Stanislav Brabec wrote:
> It implies, that all subsequent logic expressions in probe_ext* are
> inconsistent and makes no sense as well. Additionally, I guess that some
> of these checks are incorrect per self. (As long as only one
> probe_ext?() returns success, then blkid returns at least something.)

commit a1ca32fb3862ccac7275d6b342805b6d99f20e39
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Tue Dec 3 16:24:44 2013 +0100

    libblkid: Identify extN file system properly


  Karel


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      reply	other threads:[~2014-04-09  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 21:52 libblkid: check for ext* is deeply broken Stanislav Brabec
2014-04-09  7:43 ` Karel Zak [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=20140409074342.GO22126@x2.net.home \
    --to=kzak@redhat.com \
    --cc=sbrabec@suse.cz \
    --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