Bill Shannon wrote:
hg push will put back committed changes even though there are other
changes in progress (i.e., files "checked out")

This makes sense to me. If you haven't committed your changes in progress, why would you want them pushed?

hg push doesn't "sccs get" / "hg update" the parent.

This also makes sense to me. What if the parent was in the middle of a compilation when a push happened? You don't want things to be changed from beneath you.

There seems to be no equivalent to the "-n" options to bringover
and putback.

This would be nice. (for people unfamiliar with Teamware, '-n' allows you to see what would be pulled/pushed without actually doing so)

There's no way to supply putback comments.

This also makes sense. Teamware allowed this because SCCS delta comments were at the file level. With a changeset model, why would the putback comment be different from the changeset comment?

No support for SCCS keywords, or anything like them, in files.

This is something we're working on. Rich Lowe and I (and possibly others) took passes are keyword filtering, though Rich did more recent work - my attempt was a long time ago. We both hit roadblocks though; and I set my attempt aside to work on more pressing matters.

No version numbers for files, only unreadable changeset ids.

This has been a matter of debate. I personally don't see the value in embedding version numbers in files. If you really need them to identify a file, the changeset id, or revision number (if you want a monotonically increasing number - though this is not canonical and may vary depending on your repository) should be sufficient.

I'm curious as to whether anyone is working to improve or
customize Mercurial so that it works more like Teamware.  In
particular, I'm curious as to what the plan is for replacing
(or eliminating) SCCS keywords and version numbers in OpenSolaris.

I would like to see some discussion about those two as well. Thanks for bringing this up Bill.

cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to