X-Spam-Checker-Version: SpamAssassin 3.3.0-rupdated (updated) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.0-rupdated Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n0UIQQoh044522 for ; Fri, 30 Jan 2009 12:26:27 -0600 Received: from attica.americas.sgi.com (attica.americas.sgi.com [128.162.236.44]) by relay3.corp.sgi.com (Postfix) with ESMTP id 0FF85AC014 for ; Fri, 30 Jan 2009 10:25:42 -0800 (PST) Received: by attica.americas.sgi.com (Postfix, from userid 44682) id 3E9B81418C960; Fri, 30 Jan 2009 12:25:42 -0600 (CST) Date: Fri, 30 Jan 2009 12:25:42 -0600 From: Martin Hicks To: kdb@sgi.com Subject: git tree on oss.sgi.com Message-ID: <20090130182542.GG7872@alcatraz.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on oss.sgi.com X-Virus-Status: Clean Hi, I intend to get a git tree up on oss.sgi.com fairly soon. I haven't quite decided what the policy should be on that tree. I might have a 'dev' branch that contains what I'm working on as well as a 'release' branch with cleaned up code. The release branch would mirror I may also need a 'tip' branch to track Ingo's latest x86 tree. mh