Richard Lowe wrote: > Mike Sullivan <Mike.Sullivan at Sun.COM> writes: > > >> I know of the hg book but haven't read it yet so I don't know >> if it is all that we need, but it's probably too much to tell >> someone to read who just wants to know how to bringover like >> they used to, so I'd indeed like a teamware->hg >> cheat sheet (which would hopefully include info about wx >> operations you're used to and how they relate now in hg). I >> think I've seen one of those floating around so that might >> be done (but I don't know, and it was a long time ago). >> > > There's the SCMVolunteers page on the wiki, and I recall at least one > person at Sun having written up something with more brevity (though I > forget who). > Martin Englund >> I know the ON teamware->bridge can have its bi-weekly troubles but >> I hadn't seen hg corruption there (well, unless I interrupt >> an 'hg pull -u -v' but it's not corrupted just not updated >> completely). >> > > Corruption there, in approximate order of frequency: > > - TeamWare badness it tripped over due to its fragility. > - (TeamWare) User error requiring content to be flushed for other reasons. > > To my knowledge, nothing having to do with mercurial has gone wrong > with the bridging. >
Yeah - the bridge hasn't failed in quite a while (over a year at least) because of bridge related code. The reasons why its tripped have been due to the diff generator running on the gate side borking and generating incorrect or incomplete diffs, or the second reason Rich cited: having to flush some user's turd. Certainly nothing has happened due to Mercurial itself. cheers, steve -- stephen lau | stevel at opensolaris.org | www.whacked.net
