Crud.. You know, I thought about that after I committed.. I've somewhat taken the "I'm hellbent on moving Scarab to T2.4 and I'm ripping up Turbine 3 to let me do it" approach. Which maybe isn't customer friendly enough of me...
I believe it's possible to go and add a tag based on date, correct? Do you think it's worth adding a "PRE_ADD_AVALON_HEAD" tag to T3 that is based on the day before I committed all the new code? Eric > -----Original Message----- > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 14, 2004 7:28 PM > To: [EMAIL PROTECTED] > Subject: Re: Updated Turbine 3 to use Fulcrum Avalon Components > > > "Eric Pugh" <[EMAIL PROTECTED]> writes: > > >Hi all, > > >I wanted to give you all a heads up before I start committing things. I > >have done some *massive* refactoring of Turbine 3 that has > directly impacted > >Scarab: > > While I'm not using Turbine 3, I'd suggest that you tag the > current state before putting in your changes to allow people > whose apps break, to compare the > pre-refactoring to the HEAD. > > Regards > Henning > > -- > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire > Linux, Java, perl, Solaris -- Consulting, Training, Development > > What is more important to you... > [ ] Product Security > or [ ] Quality of Sales and Marketing Support > -- actual question from a Microsoft customer survey > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
