Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 11101 invoked from network); 18 Sep 2007 20:40:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Sep 2007 20:40:07 -0000 Received: (qmail 90415 invoked by uid 500); 18 Sep 2007 20:39:59 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 89985 invoked by uid 500); 18 Sep 2007 20:39:58 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 89974 invoked by uid 99); 18 Sep 2007 20:39:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 13:39:58 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [130.237.222.182] (HELO smtp.nada.kth.se) (130.237.222.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 20:41:52 +0000 X-Authentication-Info: The sender was authenticated as danielf using PLAIN at smtp.nada.kth.se Received: from [85.226.148.44] (c-2c94e255.188-1-64736c14.cust.bredbandsbolaget.se [85.226.148.44]) (authenticated bits=0) by smtp.nada.kth.se (8.12.11.20060308/8.12.11) with ESMTP id l8IKdYWQ024975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 18 Sep 2007 22:39:36 +0200 (MEST) Message-ID: <46F03782.3010109@nada.kth.se> Date: Tue, 18 Sep 2007 22:39:30 +0200 From: Daniel Fagerstrom User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: pipelineComponent scope troubles References: <46C95ED4.7000602@apache.org> <46E4E2CC.1090906@apache.org> <46E4FEC3.4020703@apache.org> <46E52608.7050705@apache.org> <46E5429A.1000808@apache.org> <46E67DA5.9000807@apache.org> <46E6EA9F.5000205@apache.org> <46E7F40D.1030500@apache.org> <46E80467.8090609@apache.org> <46E80EEA.2010803@apache.org> <46E9AED4.5030005@apache.org> <46EA2DEA.8020804@apache.org> <46EA5DF1.6030208@apache.org> <46EA9C9E.5010409@apache.org> <46EAA2F8.1080302@apache.org> <46EAFCCA.8000105@apache.org> <46EFC985.4080401@apache.org> <46EFCFC3.5030407@apache.org> <46EFF037.3070409@nada.kth.se> <46F00F9B.1010209@apache.org> <46F01F98.2080505@nada.kth.se> <46F029F3.30200@apache.org> In-Reply-To: <46F029F3.30200@apache.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Grzegorz Kossakowski skrev: > Daniel Fagerstrom pisze: ... >>> Sorry for little offending words but I'm really tired repeating the >>> same thing around ten times and >>> being blamed in the end. >> In general, if one repeat the same thing ten times whithout anyone >> understanding it, it just might be relevant feedback on ones >> presentation style ;) > > I would be grateful for any criticism and I am aware that my English skills are not of highest > order. I have no problems following your English, so its good enogh for me. I leave the finer details to the native speakers ;) > So here goes my humble request: > If you really have hard times understanding me or I'm just boring for too long don't hesitate to > just point it. I've already learned a lot from this community and polishing communication skills > would be great addition. :-) I'll point it out next time I have some specific suggestion. A more general suggestion is that when you use referential words like "it" or "this" I often have to make an effort to find out what you are refering to which sometimes makes it time consuming to understand what you mean. If you would be more generous in repeating what object you refer to it would help me. Concrete examples helps tremendesly for understanding things. But I'm of course aware about that they take time to construct and describe and that it is an aera where most of us could improve ;) >>> I hope that we can summarize current situation, cut new release >>> candidate of C2.2 and return back to >>> whiteboard for a while. >> Anyway, my propsal that you give an explicit description about the >> assumed state before and after the context change, is a serious >> proposal. If you have described it, please give me a link. Otherwise it >> would be really helpfull if you write it down. > > Ok, I'll write separate e-mail explaining how everything is supposed to work. Great! /Daniel