Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 62445 invoked from network); 24 Jul 2006 23:19:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Jul 2006 23:19:36 -0000 Received: (qmail 58499 invoked by uid 500); 24 Jul 2006 23:19:31 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 57848 invoked by uid 500); 24 Jul 2006 23:19:30 -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 57828 invoked by uid 99); 24 Jul 2006 23:19:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2006 16:19:30 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of eljotpl@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO py-out-1112.google.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2006 16:19:29 -0700 Received: by py-out-1112.google.com with SMTP id b36so2224983pyb for ; Mon, 24 Jul 2006 16:19:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=abLOJ39ErmrC8mA4aLZb+auC+OIumbsYRzbhKjVYDvznB+iU3jyZzoRU396v9un0WGB/auVozkRw9z/i72jsQ0YsUzY9TR89oRggfjAaWYzJl3JalSIU+Yp7UyS94ENZNHHPDowSDFnRXsBDTcEUsEnI4IBiFXQFCE+ckctc0Ss= Received: by 10.35.79.3 with SMTP id g3mr8398960pyl; Mon, 24 Jul 2006 16:19:06 -0700 (PDT) Received: by 10.35.48.10 with HTTP; Mon, 24 Jul 2006 16:19:06 -0700 (PDT) Message-ID: <1b5bfeb50607241619m2f6bd965h2d60c0eae52d6ad8@mail.gmail.com> Date: Tue, 25 Jul 2006 01:19:06 +0200 From: "Jacek Laskowski" Reply-To: jacek@laskowski.net.pl Sender: eljotpl@gmail.com To: dev@geronimo.apache.org Subject: Re: Re: [RTC] Merge m2migration (functional m2 build) to trunk In-Reply-To: <937046e80607241608o40a68c4ao1e1d21b9ad9bb6d8@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <22DECB18-439D-4485-ACFC-80B12243C737@planet57.com> <1b5bfeb50607240116t6f4785a3p859fb6a930c83f2a@mail.gmail.com> <1b5bfeb50607240211y779e1282m52e89bec36a42ae0@mail.gmail.com> <219AE771-07CF-45CF-8160-F4150920A39C@planet57.com> <1b5bfeb50607241511s1ed0d5f3ob70aaaa9792dc536@mail.gmail.com> <09745891-A6F2-4A21-8DD7-0E92DDC47EE6@planet57.com> <44C54FEA.5010409@apache.org> <937046e80607241608o40a68c4ao1e1d21b9ad9bb6d8@mail.gmail.com> X-Google-Sender-Auth: 4d73f152b78fd8f6 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/25/06, Jason Dillon wrote: > So far I've responded to Jacek several times about creating an issue. > The first was a response to a question if he should create an issue, > and I said yes. So after several more emails still talking about no > issue and me responding with affirmation to create one... I really > don't have much more patience nor do I really know to best and > constructively respond to a situation like that. > > And I really, really don't see how else I could have possibly > responded to his statement in any other constructive manner, about not > understanding my query after I had though that I really, clearly > stated exactly what I was asking. And honestly I still don't know what I should include in the jira issue. Sorry. I'm trying to grasp it, but...hey it's not an issue! ;-) It's in the m2migration branch, so how could I report an issue when it's a forked development area? It's under development and it needs to be fixed with no official statements. If I were to report each and every issue in a branch, jira would quickly get out of sync with reality. Am I correct? Jacek -- Jacek Laskowski http://www.laskowski.net.pl