From: Paul S. <pv...@gm...> - 2009-11-23 22:30:36
|
ok. I'm fine with that and will tag prior to commting any DUnit2-related material on the trunk. My concern was disrupting anybody working off the head - but I guess that's life on the bleeding edge... Cheer, Paul. On Tue, Nov 24, 2009 at 7:14 AM, Mark Edington (Embarcadero) < med...@us...> wrote: > On 11/23/2009 2:24 AM, Kris Golko wrote: > > I suggest we _tag_ the source after Embarcadero changes are complete. > Then, we can procede with merging DUnit2 changes. > > I don't see a point in branching, as we don't need to develop two source > streams. A tag can be used as a brach if such need arises. > > > I don't have any other changes to commit from Embarcadero at this time. > > I'm inclined to agree with Kris about using a tag for DUnit1 instead of > branching to do the DUnit2 the merge. It'll be less work that way and also > keep the important change history on the trunk. > > Mark > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Dunit-interest mailing list > Dun...@li... > https://lists.sourceforge.net/lists/listinfo/dunit-interest > > |