On 03/03/2010 17:53, Bernd Eilers wrote: > If we would want to be able to directly set the CWS to 'new' in EIS for > HG based ChildWorkspaces for everyone we could probably add such a > feature, but it would eventually be some kind of tricky how to allow > that than for HG based CWS and disallow that for other CWSs which are > using other SCMs.
given that OOO320 has recently been migrated to HG, the only code lines on other SCM are: OOH680 (2.4.x, on CVS) ???645 (1.1.x, on CVS) afaik there will not be further OOo releases for these code lines (and maybe 645 is completely dead), so there will only be Sun developers creating very few CWSes there for our customers that don't like to upgrade every decade. so i don't think there is any need for EIS to be especially picky about this; if a Sun developer gets it wrong, you know where their office is :) mfg michael -- "Quite frankly, I found it mostly interesting in a Jerry Springer kind of way. White trash battling it out in public, throwing chairs at each other. SCO crying about IBM's other women. ... Fairly entertaining" -- Linus Torvalds --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
