Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 95253 invoked by uid 500); 19 Apr 2002 18:13:38 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 95196 invoked from network); 19 Apr 2002 18:13:37 -0000 Message-ID: <3CC05E8F.3040609@apache.org> Date: Fri, 19 Apr 2002 14:14:39 -0400 From: "Andrew C. Oliver" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: cvs commit: xml-cocoon2/src/webapp/docs/samples/stream OrderPage.xml References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N My (not very important) opinion is that the samples are new features and dependant upon features and/or feature-oriented-bug-fixes (if you want an indepth discussion of what I mean by that...those gooey bug fixes that are hybridized features...beginning with Ancient Egypt then just ask off list ;-) ) so they should go in the HEAD and not the 2_0_3....but thats just my opinion. Consider most of the things I submit as features and/or feature oriented bugs. (I'd have to know way more than I do to fix regular bugs ;-) ) -Andy Gerhard Froehlich wrote: >>From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] >> >>>Is patching of your goes to both branches or not? >>> >>Ahem.... no? ;-) >> >>What do I have to do, tag it? (I've never worked with 2 branches together >>before) >> > >Check out both branches HEAD and cocoon_2_0_3_branch in 2 different >directories, apply the patches in each directory and commit it. > >Then the changes will go in the correct branch. > > ~Gerhard > >--------------------------------------------- >Very funny, Scotty. Now beam down my clothes. >--------------------------------------------- > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org >For additional commands, email: cocoon-dev-help@xml.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org