From kato-dev-return-103-apmail-incubator-kato-dev-archive=incubator.apache.org@incubator.apache.org Thu Apr 02 09:07:31 2009 Return-Path: Delivered-To: apmail-incubator-kato-dev-archive@minotaur.apache.org Received: (qmail 54071 invoked from network); 2 Apr 2009 09:07:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 09:07:31 -0000 Received: (qmail 34000 invoked by uid 500); 2 Apr 2009 09:07:31 -0000 Delivered-To: apmail-incubator-kato-dev-archive@incubator.apache.org Received: (qmail 33980 invoked by uid 500); 2 Apr 2009 09:07:31 -0000 Mailing-List: contact kato-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kato-dev@incubator.apache.org Delivered-To: mailing list kato-dev@incubator.apache.org Received: (qmail 33970 invoked by uid 99); 2 Apr 2009 09:07:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 09:07:31 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of spoole167@googlemail.com designates 209.85.219.172 as permitted sender) Received: from [209.85.219.172] (HELO mail-ew0-f172.google.com) (209.85.219.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 09:07:21 +0000 Received: by ewy20 with SMTP id 20so433023ewy.12 for ; Thu, 02 Apr 2009 02:07:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=5GCwqO0Onpbu1whiKAiWxMBMguik/CoPmwsk9U0kZwM=; b=LeyP/jlKbLM3+WPV9qg116oZcMvSjrc7HdvUsCNFj64VdE7o3YmiWJreSidjn3um9M r4UbJGgxPVtYN5YCGYVBVAtJJb1uUTd0T3wmWbkOnMu6JIjFwFgEXjNysnEaxylMI+Yc WUdAZcegBUiKJVQxRqv7fmfceQeJhCCmuL/p0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Q26d6A8woqzcSWcNRvizCrNlcH7JIMzbmjtO0/f/LMUp4WdCvZIcXTxzTbCquW/81g EV7ulqMoRZ013t3tZRsEzeJlvAKbFbLy44WAMvuC9g1HhioOYjqGWpF5Zdehs+trOyuB hcA0Ccns2kCEu4Xri0AxrV5hZC+KELEN+iI6Y= MIME-Version: 1.0 Received: by 10.216.55.201 with SMTP id k51mr2921789wec.184.1238663221239; Thu, 02 Apr 2009 02:07:01 -0700 (PDT) Date: Thu, 2 Apr 2009 10:07:01 +0100 Message-ID: Subject: How to deal with a log jam of code From: Steve Poole To: kato-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6dbe2ae4c78d704668ec1d6 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dbe2ae4c78d704668ec1d6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all. During the time we've been waiting for the CCLA etc from IBM to kickstart the Kato project we've been working on some of the other development items needed by Kato. We now have a simple hprof reader for Kato and a hex dump viewer. I'm concious that we need to show where it all came from - its not additional seed contributions from IBM. Its just a backlog of stuff that would have been developed in Apache Kato but didn't due to initial setup conditions. I'd plan for us just to book it all in to svn under a couple of well documented commits - is that ok? Steve --0016e6dbe2ae4c78d704668ec1d6--