From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from icarus.com (icarus.icarus.com [64.105.89.2]) by ozlabs.org (Postfix) with ESMTP id 1964F67A6C for ; Sat, 18 Jun 2005 04:22:40 +1000 (EST) Received: from [192.168.1.7] (wing [192.168.1.7]) (authenticated) by icarus.com (8.11.6/8.11.6) with ESMTP id j5HHkcP23191 for ; Fri, 17 Jun 2005 10:46:38 -0700 Message-ID: <42B30C7E.7040007@icarus.com> Date: Fri, 17 Jun 2005 10:46:38 -0700 From: Stephen Williams MIME-Version: 1.0 To: linuxppc-embedded@ozlabs.org Content-Type: text/plain; charset=us-ascii; format=flowed Subject: Active 2.4 kernel repositories List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a 405GPr based custom board that is running Linux 2.4, and we want to stay there for the while. I've been keeping up to date (more or less) with the linuxppc-2.4 BitKeeper tree but that tree is done now and I would like to point at a managed tree (CVS, git, whatever) that I can use to keep my board support patches up to date against. I can of course go to kernel.org and get the latest kernel trees from there, but I really would rather follow an actively maintained tree. So what's the story? Maybe there is a community managed tree where I can submit my board support patches? - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCswx9rPt1Sc2b3ikRApGwAJ9W+t/cPY1mGuy3qses8e0QuLV4NACcDYlI KUwD6QsYb1N40vqH8WhdhDQ= =VWMT -----END PGP SIGNATURE-----