From dev-return-30395-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Jun 02 14:15:26 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 38985 invoked from network); 2 Jun 2006 14:15:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jun 2006 14:15:25 -0000 Received: (qmail 31421 invoked by uid 500); 2 Jun 2006 14:15:17 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 31172 invoked by uid 500); 2 Jun 2006 14:15:16 -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 31085 invoked by uid 99); 2 Jun 2006 14:15:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2006 07:15:16 -0700 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 eljotpl@gmail.com designates 64.233.166.182 as permitted sender) Received: from [64.233.166.182] (HELO py-out-1112.google.com) (64.233.166.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2006 07:15:14 -0700 Received: by py-out-1112.google.com with SMTP id x31so1048045pye for ; Fri, 02 Jun 2006 07:14:53 -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=lZ73xKlQ4SkE/8HBAnCBxoO566NIVnli2w4m1maVKXnZtUGwqB/ON7gZ+schaZ7k2M6CJ/2ScyrPxF4tAQwYRVGdUl4dWLErrAtFDWdWeF4php4ShV5+FbXW1I5utnPNCp5NB868ZmH6iIk7+BemozRjgGjpLIhmxvR4luD2K+Y= Received: by 10.35.88.17 with SMTP id q17mr2458114pyl; Fri, 02 Jun 2006 07:14:53 -0700 (PDT) Received: by 10.35.54.13 with HTTP; Fri, 2 Jun 2006 07:14:53 -0700 (PDT) Message-ID: <1b5bfeb50606020714t7e2dc75ci90bab3553ef9182b@mail.gmail.com> Date: Fri, 2 Jun 2006 16:14:53 +0200 From: "Jacek Laskowski" Reply-To: jacek@laskowski.net.pl Sender: eljotpl@gmail.com To: dev@geronimo.apache.org Subject: Re: RTC Does Not Apply To Merging ANYTHING in dead-1.2 into trunk In-Reply-To: <94AE0B2C-3723-4E7B-A788-3CCAAC9BECEA@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <94AE0B2C-3723-4E7B-A788-3CCAAC9BECEA@yahoo.com> X-Google-Sender-Auth: 1604a268fb5838c9 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 6/2/06, David Jencks wrote: > Several people have asserted the claim in the subject above and > AFAICT no one on the board or PMC have argued with it. I'm going to > assume there are no objections. +1 > In particular I plan to check that the m2 patches don't break the > trunk build and apply them. Does it mean you're applying the already-checked-in patches wrt M2 from dead-1.2 to the trunk? I'm asking this as I don't want to duplicate it or make things broken after applying some of them before you. > david jencks Jacek -- Jacek Laskowski http://www.laskowski.net.pl