Darren J Moffat wrote:
Danek Duvall wrote:
> Worst comes to worst, it probably won't be all that difficult to write a
wx->hg bridge, but I don't really think we'll have to go that far, unless
we get a lot of cranky old ON engineers who refuse to change their ways.
Okay, we might have to do it. :)
My preference is that wx(1) as a command should die it is a teamware
helper and we are going to Mercurial.
There is enough of a concept change in Teamware to Mercurial that I
think it is actually better if the CLI is completely changed.
If said crankypants people want aliases they can write them but we
should embrace the Mercurial way - don't fight it by trying to model
Teamware/wx behaviours in hg or hg extensions or wrappers.
+1
(which is why I think writing a Mercurial extension to do things like
checks, etc. makes the most sense)
It also reduces the engineering effort for porting wx, since we can
"leave" wx as-is for Teamware support, and move onto better things for
Mercurial.
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
