From dev-return-19049-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Tue Nov 01 22:10:03 2005 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 58401 invoked from network); 1 Nov 2005 22:10:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Nov 2005 22:10:03 -0000 Received: (qmail 87094 invoked by uid 500); 1 Nov 2005 22:10:02 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 86373 invoked by uid 500); 1 Nov 2005 22:09:59 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 86362 invoked by uid 99); 1 Nov 2005 22:09:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 14:09:58 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of brett.porter@gmail.com designates 66.249.82.193 as permitted sender) Received: from [66.249.82.193] (HELO xproxy.gmail.com) (66.249.82.193) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 14:09:54 -0800 Received: by xproxy.gmail.com with SMTP id i28so650077wxd for ; Tue, 01 Nov 2005 14:09:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=upyQpBe7rQwkVx5hWAnpygmWOwbwXvUKaGzwMtGAWY3fwtUv/CIqZ2z9iT2vntrn0pczxQThNwW9tbRdszQTBu6SycYPOoM7CxiaSZSxKLfW4sgje0vO30+9jqs6yC8kCJ1VlumK1gBwS9cISgZzrpDU3T0NQCqMyeKwl6ynHQQ= Received: by 10.70.20.14 with SMTP id 14mr2732697wxt; Tue, 01 Nov 2005 14:09:37 -0800 (PST) Received: by 10.70.40.13 with HTTP; Tue, 1 Nov 2005 14:09:37 -0800 (PST) Message-ID: <9e3862d80511011409q3ecb4753xdd8d3b9c5173321f@mail.gmail.com> Date: Wed, 2 Nov 2005 09:09:37 +1100 From: Brett Porter To: dev@geronimo.apache.org Subject: Re: How to identify a JIRA with a patch. In-Reply-To: <4367E660.6090300@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4367E660.6090300@earthlink.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Not as far as I know. I'm tracking a JIRA ticket at Atlassian for the ability to detect the existence of an attachment, but that stiff doen't designate if its a patch unfortunately. In our project we just query for "patch" in any of the text fields. We generally find that people type that somewhere when attaching it. - Brett On 11/2/05, Joe Bohn wrote: > Is there any way to get a view of JIRAs that have files(patches) attached= ? > > If not, can we begin some kind of convention? I noticed that some folks > have added (Patch) to the start of the title for a few JIRAs. Do you > think that would be helpful? > > I image it must be a pain for the committers to get a view of the > available patches. > > Any other suggestions? Anybody how other projects manage this? > > Joe >