public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Cohen <lkml@ohdarn.net>
To: "Craig I. Hagan" <hagan@cih.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New tree started ;)
Date: 31 Dec 2001 17:37:37 -0500	[thread overview]
Message-ID: <1009838257.8715.1.camel@ohdarn.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0112311415110.16124-100000@svr.cih.com>
In-Reply-To: <Pine.LNX.4.33.0112311415110.16124-100000@svr.cih.com>

On Mon, 2001-12-31 at 17:17, Craig I. Hagan wrote:
> 
> I'd include trond's nfs patches @   
> http://www.fys.uio.no/~trondmy/src/2.4.17/linux-2.4.17-NFS_ALL.dif

Great, I'll take a look. thanks.

> I was planning on starting a tree similar to yours, but with a focus towards
> things that folks would want for a servers and/or HPC clustesr as soon as i
> have time (target is end of month +/-). however, i'll bet that there would be a
> serious amount of overlap, making it possible to share bitkeeper stuff, etc.

Server stuff is important to me too, though -preempt and such are for
workstations. Once 2.4.18 is released I'm going to include ppc fixes as
well. 

------
Michael Cohen
OhDarn.net

	        "Intelligence is the ability to do no work, yet somehow
		getting the work done."
                -- Linus Torvalds :)


       reply	other threads:[~2001-12-31 22:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0112311415110.16124-100000@svr.cih.com>
2001-12-31 22:37 ` Michael Cohen [this message]
     [not found] <200201012342.PAA14236@cesium.transmeta.com>
2002-01-02  2:18 ` New tree started ;) Michael Cohen
2002-01-02  2:24   ` H. Peter Anvin
2001-12-31 21:45 Michael Cohen
2001-12-31 22:07 ` William Lee Irwin III
2002-01-02 16:09   ` george anzinger
2002-01-01 10:22 ` Roberto Nibali
2002-01-01 11:01   ` Yoann Vandoorselaere

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=1009838257.8715.1.camel@ohdarn.net \
    --to=lkml@ohdarn.net \
    --cc=hagan@cih.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