From: Oleg Drokin <green@namesys.com>
To: JP Howard <jh_lists@fastmail.fm>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Recommended patches for mail server?
Date: Tue, 15 Oct 2002 16:29:23 +0400 [thread overview]
Message-ID: <20021015162923.A992@namesys.com> (raw)
In-Reply-To: <20021015105521.71AE11AEC14C@server5.fastmail.fm>
Hello!
On Tue, Oct 15, 2002 at 10:55:21AM +0000, JP Howard wrote:
> > They should apply cleanly, if you are worried about some offsets, this is
> > ok and should not concern you. (just use -s switch to patch command
> > to not see unneeded output ;) )
> I got quite a few HUNK FAILED. Also, I found that with the data logging
> patches these other patches didn't apply cleanly.
Hm. You apply the patches in order, is that right?
> Could you please tell me which, if any, of these patches are important?
> Also, I noticed 07-mmaped_data_loss_fix.diff here:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0201.3/1161.html
07-mmaped_data_loss_fix.diff is in 2.4.19 already, may be you are just
downloading patches from the wrong dir?
> Since Cyrus mmap()s files which it also opens directly, is this an
> important patch? Any others of these 2.5 patches? Are they backported to
It is importnt, but is included already.
> 2.4?
Other patches are some cosmetic cleanups, also new block allocator,
but this block allocator is uncompatible with Chris' data logging patches yet,
and you need Chris' patches more. There also this NFS fix I recommended and
two not very important fixes that you would probably never ever need.
(fixes are patches 13-remount-rw-fix.diff and 04-item_alignment_fix.diff)
Bye,
Oleg
next prev parent reply other threads:[~2002-10-15 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 10:55 Recommended patches for mail server? JP Howard
2002-10-15 12:29 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 22:25 JP Howard
2002-10-15 9:48 JP Howard
2002-10-15 10:00 ` Oleg Drokin
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=20021015162923.A992@namesys.com \
--to=green@namesys.com \
--cc=jh_lists@fastmail.fm \
--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.