public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Roberto Rivera <rrivera@ucwphilly.rr.com>
Cc: Linux <linux-kernel@vger.kernel.org>
Subject: Re: ANNOUNCEMENT: XFS patches with rmap12d + 2.4.18-pre9 +
Date: 13 Feb 2002 10:16:53 -0500	[thread overview]
Message-ID: <1013613440.10871.8.camel@unaropia> (raw)
In-Reply-To: <3C69D772.6070008@ucwphilly.rr.com>
In-Reply-To: <3C675D14.8000508@ucwphilly.rr.com> <1013499043.3533.1.camel@coredump>  <3C69D772.6070008@ucwphilly.rr.com>

Most appreciated. I will apply, I've been slow fixing shawn4 because I'm
in the process of merging some of my trees into a more clean structure. 

I can't use bk because it won't let me merge 2.4.17 vanilla, and SGI's
CVS tree into one with tag/branches. CVS does (sort of) so I have to
keep CVS.

For my custom branch, I have bk setup, I can just import the changes
from XFS tree as a GNU diff and merge it in.

As for rmap, I'll just keep getting the diffs from his website, since I
don't want another kernel tree to deal with :-)

Shawn.

On Tue, 2002-02-12 at 22:03, Roberto Rivera wrote:
>   Hi Shawn,
> Created an incremetal patch to shawn4 for pre7ac3 to pre9ac2, which I've 
> attached in case you were interested.
> Your shawn4 has worked great so far. I even have the preempt-O1-K3 patch 
> applied. This is the first 2.4.18pre kernel that has been able to stay 
> up all night without crashing. :) I'm going to keep my computer on to 
> see how long it will stay up before I try the new patch.
> 
> Thanks,
> Rob
> 
> Shawn Starr wrote:
> 
> >See site, new patches
> >
> >New fix coming today though -shawn5
> >
> >quota support broken compiling -- fixing today
> >
> >XFS + EXT2/EXT3 = superblock fails to be detected, another person ran
> >into this as well. unsure yet.
> >
> >Shawn.
> >
> >On Mon, 2002-02-11 at 00:56, Roberto Rivera wrote:
> >
> >>Hi Shawn,
> >>I downloaded your patches:
> >>
> >>Didn't find:
> >>  xfs-2.4.18-pre9-shawn1
> >>  containing: ac3 rmap12d and xfs
> >>
> >>Seemed to only have the xfs changes.
> >>Did I miss something?
> >>
> >>Rob
> >>



  parent reply	other threads:[~2002-02-13 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C675D14.8000508@ucwphilly.rr.com>
2002-02-11  6:34 ` ANNOUNCEMENT: XFS patches with rmap12e + 2.4.18-pre9 + Shawn Starr
2002-02-12  7:35   ` ANNOUNCEMENT: XFS patches with rmap12e + 2.4.18-pre9 Shawn Starr
2002-02-13 15:54     ` Steve Lord
     [not found] ` <1013499043.3533.1.camel@coredump>
     [not found]   ` <3C69D772.6070008@ucwphilly.rr.com>
2002-02-13 15:16     ` Shawn Starr [this message]
2002-02-10  2:36 ANNOUNCEMENT: XFS patches with rmap12d + 2.4.18-pre9 + Shawn Starr

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=1013613440.10871.8.camel@unaropia \
    --to=spstarr@sh0n.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rrivera@ucwphilly.rr.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