public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Walt H <waltabbyh@comcast.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-ck5
Date: Sat, 12 Apr 2003 01:11:40 +1000	[thread overview]
Message-ID: <200304120111.40406.kernel@kolivas.org> (raw)
In-Reply-To: <3E96D9B5.5060704@comcast.net>

On Sat, 12 Apr 2003 01:05, you wrote:
> Con Kolivas wrote:
> > XFS must be responsible. I can't test it fully myself but it appears to
> > be related to the latest xfs update I've included in -ck5 which is a
> > snapshot from the sgi website only a week old. Until further notice, use
> > ck4 if you wish to use XFS.
> >
> > Thanks for the feedback.
> >
> > Con
>
> Thanks Con. Now that I think about it, I probably should've cc'd the xfs
> list. There was some work done on memory leaks in XFS recently -
> something in here must expose additional leaks. Thanks again,

No problem. I need the feedback. There is no point cc'ing the xfs list because 
my patch is an altered version so I cant be certain that it's the xfs patch 
or my merging responsible unless you try the patch by itself from their 
website. It's up to you if you have the time and inclination to do this.

Con

  reply	other threads:[~2003-04-11 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 14:54 2.4.20-ck5 Walt H
2003-04-11 15:01 ` 2.4.20-ck5 Con Kolivas
2003-04-11 15:05   ` 2.4.20-ck5 Walt H
2003-04-11 15:11     ` Con Kolivas [this message]
2003-04-11 15:34     ` 2.4.20-ck5 Con Kolivas
2003-04-11 15:58       ` 2.4.20-ck5 Walt H
2003-04-11 16:45 ` 2.4.20-ck5 Bob Johnson
2003-04-11 16:58   ` 2.4.20-ck5 Con Kolivas
2003-04-11 17:12     ` 2.4.20-ck5 Bob Johnson
2003-04-15  1:41 ` 2.4.20-ck5 Daniel Gryniewicz
2003-04-15  2:06   ` 2.4.20-ck5 Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09 14:50 2.4.20-ck5 Con Kolivas

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=200304120111.40406.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waltabbyh@comcast.net \
    /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