linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Karel Zak <kzak@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>,
	linux-ext4@vger.kernel.org,
	Scott James Remnant <scott@ubuntu.com>
Subject: Re: [PATCH] blkid: add --disable-libblkid (v2)
Date: Fri, 17 Apr 2009 15:36:45 +0200	[thread overview]
Message-ID: <ac3eb2510904170636u15992e6axfba3e672f37aba4@mail.gmail.com> (raw)
In-Reply-To: <20090416102241.GA3290@nb.net.home>

On Thu, Apr 16, 2009 at 12:22, Karel Zak <kzak@redhat.com> wrote:
> On Tue, Mar 24, 2009 at 12:11:47PM +0000, Scott James Remnant wrote:
>> Karel Zak wrote:
>>
>> > I found some bugs in my previous patches. Please, use the patch
>> > below. This patch includes all necessary changes. Sorry.
>> >
>> When putting together an Ubuntu package with this patch, I found that it
>> ends up putting the pkg-config output into the make dependency variables
>> and thus fails because it can't make the "-L/lib" target.
>>
>> The attached patch fixes that, and includes your previous patch.
>
>  Ted, ping ping ping... :-) Please, we need your feedback.

Ted? Please make sure we get this in.

You will save people not using Fedora, SUSE, Ubuntu, finding out why
recent tools they try to build/install will stop working for them,
when they don't have these patches. We are going to introduce hard
dependencies on the the new libblkid from util-linux-ng for a bunch of
upstream projects.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-17 13:37 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 [this message]
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
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=ac3eb2510904170636u15992e6axfba3e672f37aba4@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=kzak@redhat.com \
    --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).