Mike Kupfer writes: > I agree with you about what 461 covers, but I want to make sure we're > all on the same page about what we're delivering. I *don't* want to be > saying we're ready for code review, except the fine print says we still > have some development work to do, like a merge GUI.
OK. > Jim> Having a GUI is (I think) about making contributions from the > Jim> outside more plausible than they are today. > > Lack of a GUI is a serious regression from the current TeamWare-based > environment. Internal users have Teamware filemerge before and after the tools putback. External users have no filemerge before and after the putback. I don't think we're talking about a regression ... at least for the tools putback, and likely after that point as well. We're talking about a "regression" only if external users expect to see the same tools available or if the internal users suddenly become external. (Do you know something about a coming RIF/reorg that I don't? ;-}) > Internal developers can use FileMerge, but I was concerned > that we might have to write a wrapper. But now that I reread Matt's > email about the new merge configuration syntax, it looks like a wrapper > will be unnecessary. OK. > We'll still need to make some changes to hgsetup. Since those changes > should be just a couple lines, and they'll be difficult to test without > Mercurial 1.0, I don't think they need to block the code review. That makes sense to me. I doubt reviewers will dwell much on the details inside hgsetup anyway. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
