All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Benjamin Herrenschmidt <bh40@calva.net>
Cc: jlquinn@us.ibm.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Building 2.3.35?
Date: Thu, 6 Jan 2000 12:21:19 -0800	[thread overview]
Message-ID: <20000106122119.A2174@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10001062117021.11905-100000@callisto.of.borg>; from Geert Uytterhoeven on Thu, Jan 06, 2000 at 09:17:25PM +0100


I'm taking a more active role in keeping the PPC/linux/BK trees working.
Please bug me on a regular basis if you have problems.  

I'm in the middle of cloning the trees to bitkeeper.com and I'll be putting
bitkeeper.com on the net as a big fast machine that I'll let anyone into to
do work.

On Thu, Jan 06, 2000 at 09:17:25PM +0100, Geert Uytterhoeven wrote:
> 
> On Thu, 6 Jan 2000, Benjamin Herrenschmidt wrote:
> > On Thu, Jan 6, 2000,  <jlquinn@us.ibm.com> wrote:
> > >2.3.35 is the first unstable kernel that I've put some effort in getting to
> > >build.  I only get to play with stuff for 2-3 hours a week, so it's hard to
> > >really do debugging at the rate of kernel development :-)
> > >
> > >How does merging of the vger tree into Linus' development kernel work right
> > >now?
> > 
> > The main ppc tree, for now, is not vger but Cort's bitkeeper. (I don't
> > know if Cort keeps vger updated).
> 
> Vger is no longer kept up-to-date, except through Linus (which isn't up-to-date
> neither :-(
> 
> Gr{oetje,eeting}s,
> --
> Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> 							    -- Linus Torvalds
> 

-- 
---
Larry McVoy            	   lm@bitmover.com           http://www.bitmover.com/lm 

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-06 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 15:49 Building 2.3.35? jlquinn
2000-01-06 16:19 ` Benjamin Herrenschmidt
2000-01-06 20:17   ` Geert Uytterhoeven
2000-01-06 20:21     ` Larry McVoy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-01-06 15:25 jlquinn
2000-01-06 15:38 ` Andreas Tobler

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=20000106122119.A2174@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=bh40@calva.net \
    --cc=geert@linux-m68k.org \
    --cc=jlquinn@us.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.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 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.