From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Matthias Koenig <mkoenig@suse.de>,
linux-ext4@vger.kernel.org, hvogel@suse.de,
Girish Shilamkar <Girish.Shilamkar@Sun.COM>,
Eric Sandeen <esandeen@redhat.com>
Subject: Re: Integrating patches in SLES10 e2fsprogs
Date: Mon, 28 Jan 2008 00:24:15 -0500 [thread overview]
Message-ID: <20080128052415.GA23482@mit.edu> (raw)
In-Reply-To: <479D5CB9.5060801@redhat.com>
On Sun, Jan 27, 2008 at 10:40:25PM -0600, Eric Sandeen wrote:
>
> %build
> aclocal
> autoconf
> %configure --enable-elf-shlibs --enable-nls --disable-e2initrd-helper
> --enable-blkid-devmapper --enable-blkid-selinux --enable-dynamic-e2fsck
> make %{?_smp_mflags}
>
It should be fine if you eliminate the "aclocal" call. And I've never
understood why people like to regenerate configure scripts from
configure.in in the first place....
In any case, I've just released e2fsprogs 1.40.6. It contains some of
obviously correct patches from the Novell and Red Hat packages. More
importantly, it includes the "mke2fs -E test_fs" feature which will be
needed once we push test_fs ext4 patches to mainline, which I plan to
push to Linus in the next day or two.
- Ted
next prev parent reply other threads:[~2008-01-28 5:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 21:17 Integrating patches in SLES10 e2fsprogs Andreas Dilger
2008-01-24 21:27 ` Eric Sandeen
2008-01-25 15:22 ` Matthias Koenig
2008-01-27 5:05 ` Theodore Tso
2008-01-27 15:06 ` Eric Sandeen
2008-01-27 20:27 ` Theodore Tso
2008-01-28 4:40 ` Eric Sandeen
2008-01-28 5:24 ` Theodore Tso [this message]
2008-01-28 5:43 ` Eric Sandeen
2008-01-28 16:01 ` Thierry Vignaud
2008-01-28 16:06 ` Thierry Vignaud
2008-01-28 17:03 ` Theodore Tso
2008-01-28 17:00 ` Theodore Tso
2008-01-28 15:26 ` Matthias Koenig
2008-01-28 15:38 ` Theodore Tso
2008-01-28 16:54 ` Eric Sandeen
2008-01-28 20:59 ` Andreas Dilger
2008-01-29 13:52 ` Matthias Koenig
2008-01-29 14:35 ` 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=20080128052415.GA23482@mit.edu \
--to=tytso@mit.edu \
--cc=Girish.Shilamkar@Sun.COM \
--cc=esandeen@redhat.com \
--cc=hvogel@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=mkoenig@suse.de \
--cc=sandeen@redhat.com \
/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).