Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 93114 invoked from network); 24 May 2007 21:53:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 May 2007 21:53:25 -0000 Received: (qmail 57204 invoked by uid 500); 24 May 2007 21:53:29 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 57177 invoked by uid 500); 24 May 2007 21:53:29 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 57168 invoked by uid 99); 24 May 2007 21:53:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2007 14:53:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [204.127.225.92] (HELO alnrmhc12.comcast.net) (204.127.225.92) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 May 2007 14:53:23 -0700 Received: from [192.168.168.15] (c-71-202-24-246.hsd1.ca.comcast.net[71.202.24.246]) by comcast.net (alnrmhc12) with ESMTP id <20070524215301b1200l0op6e>; Thu, 24 May 2007 21:53:02 +0000 Message-ID: <4656093C.5060907@apache.org> Date: Thu, 24 May 2007 14:53:00 -0700 From: Doug Cutting User-Agent: Thunderbird 1.5.0.10 (X11/20070403) MIME-Version: 1.0 To: hadoop-dev@lucene.apache.org Subject: Re: [jira] Updated: (HADOOP-1429) RPC Server won't go quietly References: <31262590.1180038616796.JavaMail.jira@brutus> In-Reply-To: <31262590.1180038616796.JavaMail.jira@brutus> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org stack (JIRA) wrote: > [ https://issues.apache.org/jira/browse/HADOOP-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > stack updated HADOOP-1429: > -------------------------- > > Status: Patch Available (was: Open) > > Submit to hudson test build To be clear, one should always run unit tests against trunk before marking things "Patch Available". The Hudson build just confirms that for others. The reason to mark it "Patch Available" is because you think it's ready to be committed, not because you need it tested, right? Doug