From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: fix configure.in typo
Date: Wed, 21 Oct 2009 17:14:17 -0500 [thread overview]
Message-ID: <4ADF87B9.3040204@redhat.com> (raw)
In-Reply-To: <20091021215751.GB20619@mit.edu>
Theodore Tso wrote:
> On Wed, Oct 21, 2009 at 10:21:53AM -0500, Eric Sandeen wrote:
>> seems like it's not picking up the system /usr/include/blkid/blkid.h but
>> rather e2fsprogs/lib/blkid/blkid.h
>>
>
> Um, in the maint branch e2fsprogs/lib/blkid/blkid.h no longer exists
> in the Git tree. It's been renamed to e2fsprogs/lib/blkid/blkid.h.in,
> and blkid.h is only built if libblkid is enabled.
>
> Perhaps you have a stale file that wasn't deleted by git?
>
> - Ted
oh dear, maybe that's it :)
Ok, on a fresh checkout it worked...
Sorry, not sure what state I got things into.
Thanks,
-Eric
next prev parent reply other threads:[~2009-10-21 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 3:48 [PATCH] e2fsprogs: fix configure.in typo Eric Sandeen
2009-10-21 7:52 ` Theodore Tso
2009-10-21 15:21 ` Eric Sandeen
2009-10-21 21:57 ` Theodore Tso
2009-10-21 22:14 ` Eric Sandeen [this message]
2009-10-21 22:19 ` Theodore Tso
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=4ADF87B9.3040204@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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).