Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F4767065 for ; Wed, 26 Oct 2011 18:04:55 +0000 (UTC) Received: (qmail 21355 invoked by uid 500); 26 Oct 2011 18:04:54 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 21320 invoked by uid 500); 26 Oct 2011 18:04:54 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 21312 invoked by uid 99); 26 Oct 2011 18:04:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2011 18:04:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-ww0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2011 18:04:46 +0000 Received: by wwe32 with SMTP id 32so2102269wwe.20 for ; Wed, 26 Oct 2011 11:04:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=o95Bo9xuMqUvwy0l5UrTexTuB5oSXDPVlZD8cS49gjg=; b=hHt3jQ7hPgQPMLCsGoucL0oOaFMyZ1abJbFcsAjgBgnA8w+6kxLR76a2drNZGtqsqr 1ypCIo6nzgFG0USuQL3P6niIhRyjaFDJ/Gfiqy2TL+wuoCw8LBtqJDTmvPLwwpantpcU /xCXID8J4q3aFsMUljiiwHX/kpI9eJekOyLCY= MIME-Version: 1.0 Received: by 10.216.82.6 with SMTP id n6mr1304415wee.51.1319652266307; Wed, 26 Oct 2011 11:04:26 -0700 (PDT) Received: by 10.216.45.78 with HTTP; Wed, 26 Oct 2011 11:04:26 -0700 (PDT) Date: Wed, 26 Oct 2011 11:04:26 -0700 Message-ID: Subject: proposal for naming convention of patches for TRUNK From: Ted Yu To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=0016e6dd894e8f70ae04b0377c73 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dd894e8f70ae04b0377c73 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am working with Giri on a filter that should help us avoid the following (see HBASE-4377): -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12500832/EXT_ATU_05f84d32cbc0bdabf00e00bc2f3570f0.regioninfo against trunk revision . I am proposing the following convention: TRUNK patch filename should contain the word 'trunk' in a prominent manner - surrounded by either dash or dot. Valid examples are: hbase-4377.trunk.v4.txt hbase-4377-trunk.v2.patch 0001-HBASE-4377-hbck-Offline-rebuild-.META.-from-fs-data-.trunk.v3.patch This would allow Giri to write filter that correctly uploads patch for TRUNK to Jenkins for test build. Please provide your comments. --0016e6dd894e8f70ae04b0377c73--