linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Scott James Remnant <scott@ubuntu.com>,
	linux-ext4@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] blkid: add --disable-libblkid (v2)
Date: Thu, 30 Apr 2009 10:28:34 +0200	[thread overview]
Message-ID: <20090430082834.GA3774@nb.net.home> (raw)
In-Reply-To: <20090429202338.GD17797@mit.edu>

On Wed, Apr 29, 2009 at 04:23:38PM -0400, Theodore Tso wrote:
> There have been a few bug fixes and I have some requests to detect
> some new interfaces, such as VMFS, which I'll probably apply to
> e2fsprogs blkid, but I don't expect to do any API or ABI changes, and
> the only changes will be bugfixes and some new detection functions ---
> and I'll make a point of synchronizing such improvements with
> util-linux-ng.  Fair enough?

 Yes, sounds good. My plan is send you all important patches for your
 e2fsprogs version and also periodically pull from your tree.

> As far as I know there are no applications which have used
> blkid_get_library_version(), but what I would suggest is that
> util-linux-bg use a lib_version of 2.15, and people who care about

 Yes, lib_version in my tree is already 2.15.0

> blkid_get_lib_version().  I don't anticipate e2fsprogs ever going to a
> 2.x version at this point --- we'll probably just always update the
> 1.xx version, just to avoid confusion, so I don't think we need to
> worry about freezing this version number.  I'll just put in a comment
> that util-linux-nh will have a 2.x version, and that e2fsprogs will
> have a 1.x version --- not that I think anyone will really care, or
> will try to sample the version number, as long as we're careful about
> not screwing with the ABI.

 OK. Thanks.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>

  reply	other threads:[~2009-04-30  8:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 17:38 uti-linux-ng libblkid Karel Zak
2009-02-23 17:38 ` [PATCH] blkid: add --disable-libblkid to build with external libblkid Karel Zak
2009-02-24  8:44   ` [PATCH] blkid: add --disable-libblkid (v2) Karel Zak
2009-03-24 12:11     ` Scott James Remnant
2009-04-16 10:22       ` Karel Zak
2009-04-17 13:36         ` Kay Sievers
2009-04-17 13:48         ` Scott James Remnant
2009-04-22 13:33           ` Theodore Tso
2009-04-22 13:42             ` Scott James Remnant
2009-04-22 13:49               ` Theodore Tso
2009-04-22 14:07                 ` Scott James Remnant
2009-04-29 17:22                 ` Scott James Remnant
2009-04-29 20:54                   ` Theodore Tso
2009-05-05 11:30                     ` Scott James Remnant
2009-04-27  9:21             ` Karel Zak
2009-04-28 20:36               ` Karel Zak
2009-04-29 13:59             ` Scott James Remnant
2009-04-29 17:17               ` Theodore Tso
2009-04-29 20:23         ` Theodore Tso
2009-04-30  8:28           ` Karel Zak [this message]
2009-02-23 17:38 ` [PATCH] tune2fs: make findfs code optional Karel Zak
2009-03-09  1:08 ` uti-linux-ng libblkid Theodore Tso
2009-03-09 10:42   ` Karel Zak
2009-03-09 11:45   ` Karel Zak
2009-03-18 19:28   ` 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=20090430082834.GA3774@nb.net.home \
    --to=kzak@redhat.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=scott@ubuntu.com \
    --cc=tytso@mit.edu \
    /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).