mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.8-ac8
Date: Tue, 21 Aug 2001 00:22:37 -0700 (PDT)	[thread overview]
Message-ID: <20010821072237.A98EC7840B@mail.clouddancer.com> (raw)
In-Reply-To: <9lsfn5$kr2$1@ns1.clouddancer.com>
In-Reply-To: <Pine.LNX.4.33.0108201901370.30895-100000@twin.uoregon.edu> <200108210140.f7L1eQ612898@jupter.networx.com.br> <9lsfn5$kr2$1@ns1.clouddancer.com>

In clouddancer.list.kernel, you wrote:
>
>I think is fair to say that alan's tree tracks linus' rather than sync's
>with it...
>
>it's also observable that there are a few things (from the mailing list
>traffic at least) in .9 that's perhaps shouldn't be merged into ac until
>linus has returned from vaction an examined the submitted patches/twiddled
>with it a bit himself...
>
>joelja


I hope it stays that way for awhile.  I get much better performance
(subjective, don't know how to benchmark ~2-3x virtual desktop
switching) than with any recent linus kernel.  Even playing with a
little 500M SQL database doesn't hinder the system anymore.

Thanks!



>On Mon, 20 Aug 2001, Thiago Vinhas de Moraes wrote:
>
>>
>> Alan,
>>
>> I'm sorry if it was previously answered, but why your tree is currently not
>> in sync with Linus's tree?
>>
>> Regards,
>> Thiago


-- 
Windows 2001: "I'm sorry Dave ...  I'm afraid I can't do that."


  parent reply	other threads:[~2001-08-21  7:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21  0:45 Alan Cox
2001-08-21  1:35 ` Thiago Vinhas de Moraes
2001-08-21  2:05   ` Joel Jaeggli
2001-08-21  7:22   ` Colonel [this message]
2001-08-21 12:58     ` Rik van Riel
2001-08-21  2:29 ` Rik van Riel
2001-08-21  2:38 ` Masaru Kawashima
     [not found] <no.id>
2001-08-21 12:03 ` Alan Cox

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=20010821072237.A98EC7840B@mail.clouddancer.com \
    --to=klink@clouddancer.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®