From: "Stephen C. Tweedie" <sct@redhat.com>
To: ext3 users list <ext3-users@redhat.com>,
"ext2-devel@lists.sourceforge.net"
<ext2-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Stephen Tweedie <sct@redhat.com>, Andrew Morton <akpm@digeo.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Updated ext3 patch set for 2.4
Date: 14 Mar 2003 22:42:56 +0000 [thread overview]
Message-ID: <1047681775.2566.664.camel@sisko.scot.redhat.com> (raw)
Hi all,
I've pushed my current set of ext3 diffs (against Marcelo's current
tree) to
http://people.redhat.com/sct/patches/ext3-2.4/dev-20030314/
This includes:
00-merged/ diffs recently merged into 2.4
10-core-fixes-other/ misc fixes/tweaks from akpm, adilger
11-core-fixes-sct/ misc fixes/tweaks from sct
20-tytso-updates/ Ted's recent updates
21-updates-sct/ recent sct diffs pending upstream merge
40-iflush-sct/ experimental inode-flush code
50-debug/ archive of debug patches
99-deferred/ stuff being kept around for future consideration
plus
all-patches.tar.gz tarball of the above
combo-patch-10to21.patch.gz combo patch of the 10--21 dirs above
The tytso-updates includes all of Ted's recent changes, separated out as
incrementals against the first htree+orlov changes he posted a while
back, so that we can keep track of diffs. It includes his back-port of
akpm's orlov changes, plus the recent htree and noatime fixes. Oh, and
it has the requested "+htree+orlov" ext3 version string added.
The combo patch should be equivalent to Ted's latest set of htree+orlov
diffs (except containing a few extra fixes that I'll start pushing
upstream next week), but broken out in a way that makes it easier to
track the individual change history. It has had only minimal testing so
far.
Cheers,
Stephen
next reply other threads:[~2003-03-14 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 22:42 Stephen C. Tweedie [this message]
2003-03-16 8:59 ` Ralf Hildebrandt
2003-03-20 18:04 ` Stephen C. Tweedie
2003-03-20 20:33 ` Ralf Hildebrandt
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=1047681775.2566.664.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=akpm@digeo.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®