Darren J Moffat wrote:
Will Fiveash wrote:
+1 for me too. wx has a number of problems and a strong Teamware/SCCS
bias so the above makes sense. The thing I worry about is losing
functionality like:
Glad to hear that from someone who has done so much really cool work on wx!
- efficient and simple backup and restore
That should be a trivial hg extension.
- gate rules enforcement. I'm not just talking about pbchk but things
like 'wx create' actually checked the parent's deleted_files to see if
a file of the same name existed and warned the user about the
conflict. If the Mercurial way is to test for this at putback time
it's too late.
That particular example doesn't actually make sense because
deleted_files won't exist in repository after we transition the master
gate to Mercurial.
IIRC that is actually only needed because of limiations in Teamware that
surface in this area and things like cyclic rename. Mercurial best I
can tell doesn't suffer from those problems.
- efficient determination of workspace changes
hg status -mard
No, because that only lists changes that have not been committed,
rather than changes relative to your parent.
While I'm sure folks can concoct ways of doing the above if not already
supported by Mercurial it would be good if standardized ways of doing
the above were provided (be it tools or extensions, etc...).
That is what we are doing, trying to model as much as we can as
extensions, not just as hooks at push/pull time.
I, at least, would like obviously bogus things to be called out to the
user as close to the action introducing them as possible, rather than
as part of a 'nits' or 'pbchk'-like step (or even worse, on putback or
post putback), yes.
-- Rich
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
