Return-Path: Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org Received: (qmail 3843 invoked from network); 21 Jan 2008 21:19:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2008 21:19:40 -0000 Received: (qmail 53477 invoked by uid 500); 21 Jan 2008 21:19:31 -0000 Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org Received: (qmail 53461 invoked by uid 500); 21 Jan 2008 21:19:30 -0000 Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-dev@activemq.apache.org Delivered-To: mailing list camel-dev@activemq.apache.org Received: (qmail 53452 invoked by uid 99); 21 Jan 2008 21:19:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2008 13:19:30 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bruce.snyder@gmail.com designates 64.233.184.237 as permitted sender) Received: from [64.233.184.237] (HELO wr-out-0506.google.com) (64.233.184.237) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2008 21:19:02 +0000 Received: by wr-out-0506.google.com with SMTP id 71so747199wri.5 for ; Mon, 21 Jan 2008 13:19:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=bhKm0WpmfBcIMqh2ROUCx7VGp96WPCJNMrkGsiN3h4E=; b=jnXvGCA2jCVQVsEczrhaHrEeyO8TuZIuezgFACziug7pNoOreMaYi2/orV0pVWRpGtmjMEZu0yzuXwIj15zRcQCcGVcNI02u7wLGSN8dDjd13txAWNa8QiI1LCyXFr112UwaVRp02gWIFj/kj0s7J7JMuiGLGuVwO7vK7eatZIk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=M56s/kO06ZMDRn3vg8P753RU4Nq4TSYMfoEVQA4feiXopaFlHUg8uOqDmyGq3dib3Ax21JYtrFkfyhiyqgAZepI6JvnmxG5JXLFXu/TsfwNTpfTX7cWZmM2rJbFmOkySli6jDNKCkVf0CxYAWppYNBkCzbfkCH5F9BWUsTYM3H4= Received: by 10.142.187.2 with SMTP id k2mr3563535wff.83.1200950346872; Mon, 21 Jan 2008 13:19:06 -0800 (PST) Received: by 10.142.229.19 with HTTP; Mon, 21 Jan 2008 13:19:06 -0800 (PST) Message-ID: <7b3355cb0801211319k122fae31k4443b9d99c4b1e45@mail.gmail.com> Date: Mon, 21 Jan 2008 14:19:06 -0700 From: "Bruce Snyder" To: camel-dev@activemq.apache.org Subject: Re: Should I create an JIRA issue for every commit? In-Reply-To: <38720AC8-8CFE-4D04-9FBC-7AA457F6C63E@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <38720AC8-8CFE-4D04-9FBC-7AA457F6C63E@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On Jan 21, 2008 2:10 PM, Hadrian Zbarcea wrote: > Hi Roman, > > No need for jiras for simple/cosmetic changes. For the commit that Roman is asking about, he should definitely create a JIRA issue explaining the problem. Then the SVN commit log should contain the JIRA issue number so that the commit can be automatically associated with the JIRA issue. Bruce -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E