From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: new v3 2.6.4 logging/xattr patches
Date: Fri, 19 Mar 2004 11:00:05 +0300 [thread overview]
Message-ID: <405AA885.3030000@namesys.com> (raw)
In-Reply-To: <1079679539.11055.101.camel@watt.suse.com>
Chris Mason wrote:
>Hello everyone,
>
>I've just uploaded all the reiserfs patches from the suse 2.6 kernel to:
>
>ftp.suse.com/pub/people/mason/patches/data-logging/experimental/2.6.4
>
>(they should also apply to 2.6.5-rc1 and 2.6.5-rc1-mm2)
>
>These include:
>Latency fixes
>Logging performance fixes
>data=ordered support
>quota support
>xattrs and acls from Jeff Mahoney
>
>and a few random bug fixes. There's a README file in the directory with
>a some more details.
>
>The names of the files no longer start with numbers to help you figure
>out the order the patches get applied. The directory includes a file
>called series that has a list of all the patches in the proper order.
>
>There are various shell tricks to apply things in order. Or a few
>different patch management tools that understand a series file. I use
>quilt (http://savannah.nongnu.org/projects/quilt/) which is very nice.
>
>-chris
>
>
>
>
>
>
>
>
are these ready to go to Andrew or?
--
Hans
next prev parent reply other threads:[~2004-03-19 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 6:58 new v3 2.6.4 logging/xattr patches Chris Mason
2004-03-19 8:00 ` Hans Reiser [this message]
2004-03-19 14:03 ` Chris Mason
2004-03-19 15:21 ` Chris Mason
2004-03-19 19:03 ` Hans Reiser
2004-03-19 19:11 ` Chris Mason
2004-03-19 12:42 ` Christian Mayrhuber
2004-03-20 19:18 ` Chris Mason
2004-03-20 20:15 ` Dieter Nützel
2004-03-21 14:14 ` Chris Mason
[not found] ` <200403211744.11608.Dieter.Nuetzel@hamburg.de>
[not found] ` <1079888140.11058.365.camel@watt.suse.com>
2004-03-21 19:22 ` Dieter Nützel
2004-03-21 19:26 ` Dieter Nützel
2004-03-22 13:41 ` Dieter Nützel
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=405AA885.3030000@namesys.com \
--to=reiser@namesys.com \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.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 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.