From: tytso@mit.edu
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: [PATCH] [BK] 0/11 Ext2/3 Updates: Extended attributes, ACL, etc.
Date: Thu, 31 Oct 2002 03:28:29 -0500 [thread overview]
Message-ID: <E187Agn-0003b9-00@snap.thunk.org> (raw)
Hi Linus,
I've updated the ext2/3 patches for 2.5.45. All of these changes can
also be grabbed by pulling from:
bk://extfs.bkbits.net/extfs-2.5-update
Linus, please pull; these patches have been tested as part of Andrew
Morton's mm tree, and have minimal risks if the relevant config turned
off. (People have also been using the ACL and Extended Attributes
patches enabled for quite some time as well. :-)
A complete set of all of these patches can also be found at:
http://thunk.org/tytso/linux/extfs-2.5
- Ted
next reply other threads:[~2002-10-31 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 8:28 tytso [this message]
2002-11-01 0:24 ` [PATCH] [BK] 0/11 Ext2/3 Updates: Extended attributes, ACL, etc Joseph Fannin
2002-11-01 0:47 ` Joseph Fannin
2002-11-01 1:06 ` Joseph Fannin
2002-11-01 11:56 ` Roman Zippel
2002-11-01 17:28 ` [PATCH] Fix 2.5-bk build error Joseph Fannin
2002-11-02 6:54 ` Theodore Ts'o
2002-11-02 11:53 ` Roman Zippel
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=E187Agn-0003b9-00@snap.thunk.org \
--to=tytso@mit.edu \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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