From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, mkoenig@suse.de, hvogel@suse.de,
Girish Shilamkar <Girish.Shilamkar@Sun.COM>,
Eric Sandeen <esandeen@redhat.com>
Subject: Re: Integrating patches in SLES10 e2fsprogs
Date: Thu, 24 Jan 2008 15:27:16 -0600 [thread overview]
Message-ID: <479902B4.1050806@redhat.com> (raw)
In-Reply-To: <20080124211728.GA24900@webber.adilger.int>
Andreas Dilger wrote:
> Eric, I haven't looked at the FC8/9 e2fsprogs yet, but do they also have
> a ton of patches (possibly in the -pu branch), or do they track upstream
> more closely?
I try to track upstream as closely as I can; F8 had quite a lot of
patches for a while, and I got it whittled down to just a couple. I
think I'm back up to 7 though :)
Patch1: e2fsprogs-1.39-blkid-devmapper.patch
Patch2: e2fsprogs-1.38-etcblkid.patch
Patch3: e2fsprogs-1.39-mkinstalldirs.patch
Patch4: e2fsprogs-1.40.4-uuidd-tidy.patch
Patch5: e2fsprogs-1.40.4-sb_feature_check_ignore.patch
Patch6: e2fsprogs-1.40.4-blkid-ext4dev.patch
Patch7: e2fsprogs-1.40.4-no-static-e2fsck.patch
...
# look at device mapper devices -
# autoconf-foo to find ldevmapper in /lib
%patch1 -p1 -b .dm
# put blkid.tab in /etc/blkid/ - fedora-ism I think
%patch2 -p1 -b .etcblkid
# Fix for newer autoconf (#220715) - only 'cause we must
# re-run autoconf due to patch 1 IIRC
%patch3 -p1 -b .mkinstalldirs
# uuidd manpage tidyup <--- sent upstream already
%patch4 -p1 -b .uuidd-tidy
# ignore some flag differences on primary/backup sb feature checks
# sent (bad... ) patch upstream, will resend
# ignores flags set on the fly by the kernel
%patch5 -p1 -b .featurecheck
# teach blkid about ext4dev, for now
%patch6 -p1 -b .ext4-blkid
# completely clobber e2fsck.static build,
# fedora is missing some .a's, and don't need it
%patch7 -p1 -b .e2fsck-static
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
>
next prev parent reply other threads:[~2008-01-24 21:27 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 [this message]
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
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=479902B4.1050806@redhat.com \
--to=sandeen@redhat.com \
--cc=Girish.Shilamkar@Sun.COM \
--cc=esandeen@redhat.com \
--cc=hvogel@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=mkoenig@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.